Just spent 15 minutes trying to figure out how to offer feedback on your UX for new users and I see it seems I am not permitted to create an account for the forums and no public contact for people that don’t use Twitter or Telegram… but I like what you have to offer so here I am…
And here’s some experience-based product feedback I want you to consider very seriously…
You’ve placed way too much faith in your onboarding process to teach your user’s how your product works.
Why I chose Anytime:
- Saw someone give an example on Youtube as an Obsidian alternative
- I use obsidian because I used to use Notes & Notion
- I don’t like Notion having control of my data
- Apple Notes makes it almost impossible to move to another product (how the turns table)
After downloading it to my Mac & iPhone:
I know I did the onboarding, all I remember is, nothing… maybe you’re “Notion-like”(we’ll get to that), that’s it. I was busy and needed to verify it would be a viable solution before I left for a trip.
What prompted me to launch the app a second time:
- I have a rare free morning
- I have 3 project to plan that need documentation and a research reservoir
What I see on launch:
- “My Homepage” obviously not mine
- “Task Tracker” obviously not my tasks
- “Favorites” obviously not mine
- No way to add a new section, page, or note
- Left Navbar: A mix of navigating to a page and hiding all the other stuff in it
- “My Notes” in left bar, empty and no way to add a new note… Says “There are no objects in here, create the first one” but no way to add one
I find the “+” button:
- I get an “Empty” modal
- an onboarding modal pops-up on top
- it’s explaining to me about “Sets” and “Collections” using computer science reference… but I need to make a note.
- Close it…
- Never see it again, no way to find it.
- No way to make a note
- ONBOARDING ISN’T A MODAL
A pop-up walk through that jumps into term definitions is not “onboarding,” maybe it’s a tutorial, but it’s definitely a symptom that actual user onboarding has been entirely ignored in favor of the developer’s or product owner’s needs.
How we get here:
We get too close to things, we engage early adopters that love to fiddle and explore, we focus on the cool stuff developers and product owner’s want to do and we end up cutting off our heads and focussing on the cool shit that comes out the other side instead of making sure we’re making something usable.
Why we get here:
- We lean on existing paradigms we think people know and value…
- We find likeminded new adopters who know and value these things…
- We tell ourselves the best place to start is where someone else left off…
- We tell ourselves our new users will have left off where we want to begin.
- EVERYONE STARTS WITH A NEED
Spoiler alert: It’s not to learn a new idiosyncratic system that relies on in-depth knowledge of another platform that needs to start with term definitions.
What Anytype onboarding is doing:
- Here’s a messy kitchen with dishes in the sink, vegetable off-cuts and general ingredients strewn about the place
- The knife is dirty, the pots are dirty, something is in the oven
- The trashcan is full
- Your kid is screaming
- The Phone os ringing
- You have a deadline
- An email is coming in
- Let me explain set theory before you can clean up the mess we’ve created for you and get to the reason you launched the app
- ASK A USER
- What do you need this app for?
- What’s the first thing you want to do?
- Why are you downloading a new app?
- Where would expect to find clues on how this (feature or whatever) works?
- YOU”RE IN BETA, I KNOW
This is very important feedback and addressing this will decide your future.
I’m not being grandiose or self-important; Plenty of perfect products no one uses or everyone stops using for these very reasons.
I watch CEO’s, Product Owners, and Genius Developers sabotage their products like this all the time…
- BE YOU, NOT A VERSION OF THEM
I abandoned Notion over a year ago, Evernote 4 years ago, and I can’t remember the other “anything” app and Saas products I’ve used… I don’t want another them so don’t expect to learn your way of doing what they do…
I know, adapting our existing patterns is way easier than learning new patterns, but that doesn’t mean we have to present our solutions as adaptations… we just need to adapt to the existing patterns.
“This is a that,” is typically how most people present advancement that did not solve the problem “that” was designed to solve. “This is a horse, but faster” for instance…
“That was a this,” is how most people think about “this” advancement that solves the problem “that” never did solve. “An automobile is people get where they’re going” for example…
- START WHERE USERS ARE
To summarize all of the above, just give me a way to do what I need to do… not a litany of all the possible ways of doing things and the idiosyncratic terminology needed to establish an understanding of how you conceive your product should work.
I’m not saying I won’t benefit from an understanding of the nuanced differences and finer points behind all of your decisions - I simply don’t care and never have.
I don’t pickup a hammer and get people blocking me from using it until they explain the nuances of the handle construction and the specific metallurgic terms which comprise the head of the hammer… I’d rather use a rock, and will.
I know, not everything is as simple as a hammer, not every need is as simple as “must bang thing!” but every tool has affordances and I’d suggest yours especially.
- WHERE TO BEGIN
Well, step 4, obviously… but also, anything you have to explain is an affordance that should be discovered at the time of need or easily learned about when the need arises.
Find out when and where a user needs that functionality and build an affordance in that place for them to use, discover, or learn about the power of Anytype
ANSWER: You are prioritizing your own interests over your user’s needs.
It’s a lot, I know, but I really want this product for me and I’m a bit bummed.
If you want a first experience voice over and walkthrough, I’d be happy to upload it somewhere… but only if you’ll actually use it.
All the best