After 6 years and 2 million words of daily writing I feel like I've learned enough to make Ensō simpler and more accessible.
Related thread: https://news.ycombinator.com/item?id=38025073
Sometimes providing TLDR means you are providing a way for people to instantly ignore you without further thought. Maybe there is a desire to engage people who think.
Thanks for the feedback, most of my usual readers know about Ensō and it seems I forgot to leave my little bubble when writing this post!
On one hand it’s hard to disagree with the statement “it should be clear what your product does in a single glance”. In fact there’s a whole meta that’s been developed around this, with well established common wisdom on how to structure your landing page to quickly frame value to prospective users, call them to action, etc.
On the other hand it’s kind of fun to stumble upon something and feel like you missed the beginning of the conversation, and to figure things out piece by piece based on context.
I was also confused when loading this website but it led me to trying the app and it was kind of fun.
Sometimes the most optimized, clearest path isn’t necessarily the preferable one.
Untested is my playground/a place where I "work with the garage door up", so generally I allow myself for more flexibility, especially since this post is more of a devlog entry than a one-glance product page (that would be https://enso.sonnet.io). That said, I had a break from writing, so ended up putting too much content in one place, which made it harder to edit.
What's going to happen in the next few months is this: I'll post more dev/design-log style posts on untested.sonnet.io, then extract some of this information into the product page.
I'm glad that you had some fun with the app!