This is exactly the thing I kept getting stuck on — on paper it looked like a features decision, analytics and retention and conversion paths, but really it was about who shows up in the first place. Once someone has to create an account before they can try anything, you've already filtered your audience and most people don't even realize that's what happened. The session persistence thing is almost embarrassing in hindsight — I spent weeks debating accounts when the actual complaint was just "I generated something I liked and then lost it when I closed the tab." That's a ten-line fix, not an auth system. "Validate the pain point before adding the complexity that usually comes with fixing it" is genuinely a better summary than anything in the post, I'm going to be thinking about that one for a while.
This is a great example of a product decision that looks irrational on a spreadsheet but makes perfect sense when you understand why users showed up in the first place.
A lot of founders treat accounts as an obvious upgrade because they unlock analytics, retention, and monetization. But sometimes the absence of friction is the feature. Once users have to create an account, you're not just adding functionality you're changing the product experience and, potentially, the audience.
The part that stood out to me is that you solved the actual problem (session persistence) instead of implementing the assumed solution (user accounts). That's a useful product lesson: validate the pain point before adding the complexity that usually comes with fixing it.
Sometimes the best feature is the one you decide not to build.