-
What's one of the biggest challenges of a 2-year old product? Complexity! I've learned to over-communicate everything. If you like a peak behind-the-scenes of bootstrapping a product, read on ...On twitter.com
♻️ 2 Retweets ❤️ 17 Favorites Mood +2 🙂
-
Just look at this UI for a moment. There's so much going on. Buttons and information everywhere. The longer a software lives, the more complex it gets. I don't have time to constantly redesign, so I have to do the next best thing: add tooltips ...Permalink On twitter.com
-
Note how every one of these timestamps is clickable. And each, in turn, brings up a dropdown with more options. Just today I added tooltips here because "after the fact" features made this complicated even for long-time users 😕Permalink On twitter.com
-
One way I try to combat this "information bloat" is by showing it as much in-context as possible. The info that the API is a paid feature only shows up if you open the API settings from the menu.Permalink On twitter.com
-
Another way is to over communicate negative actions. - It says twice "This room is public" - The button doesn't say "Confirm" but "Delete Room" We all don't like to read. So say it twice or three times, so the user may see it once.Permalink On twitter.com
-
And then, of course, there's the documentation. It assumes nothing but explains every little detail. Even if it seems obvious to me, the maker, it's not obvious to somebody. There's a gray pen icon beside the title? Yes, that's a button and you can click there to change it!Permalink On twitter.com
-
In the beginning I felt ashamed speaking about my product. Now? I send out a newsletter, tweet, in-app notification and share on discord about every product update. And still users hardly see it once!Permalink On twitter.com
-
So you want to build a product? Get ready to explain everything! Twice or three times!Permalink On twitter.com