For the first year of building Murror, we optimized for the same metrics every other app optimizes for: daily active users, session length, screens per visit. The dashboard looked healthy. Usage was growing. We felt good about it.
But something was off. Our most engaged users were not our happiest users. People who spent the most time in the app were often the ones who left the harshest feedback. Meanwhile, users who opened the app twice a week for five minutes were writing us emails about how it changed how they handle difficult conversations.
For months, our most requested feature at Murror was a chat function. Users wanted to talk to the AI the way they talk to a friend. It seemed obvious. Every competitor had it. Every feedback form mentioned it.
Everyone tells you to ship fast. Move fast and break things. Get to market before someone else does.
I believed this for a long time. When we were building Murror, speed was everything. We pushed features weekly, sometimes daily. We celebrated every deploy like a small victory.
There's something counterintuitive about building an AI product in the mental health and self-awareness space: if you're doing it right, your users should eventually need you less.
Most product teams optimize for stickiness. More sessions, more time in app, more daily returns. But at Murror, we've been wrestling with a different question what if the goal of our product is to help someone build enough self-understanding that they don't need to open the app as often?
There is a moment that separates products people use once from products people come back to every day. It is not a feature. It is not a notification. It is the feeling that the product remembers who you are.
I have been thinking about this a lot while building Murror. We spent so much time on acquisition, onboarding funnels, and activation metrics. But the thing that actually moved our retention numbers was something much simpler: continuity.
Most people are using AI wrong and I was one of them.
For the first year, I used AI like a fancy Google. "Write me a product description." "Summarize this." "Give me 10 ideas for X." Useful? Sure. Transformative? Not really.
After our first launch on Product Hunt, our team spent a little over a month upgrading the product. There were major changes to the UI and several new features added, so the process took time from discussions and redesigning the interface to testing, fixing bugs, and updating AI prompts.
We re also a very small team, so everyone had to push themselves to give 200%. Time and resources are limited, and at the same time, we also had to work on securing funding for the next six months to keep the team running and continue developing the app.
I have been thinking about this a lot lately: why do so many AI products feel interchangeable?
You open one, you open another. Different logo, different color scheme, same experience. A text box. A chat interface. Some version of "ask me anything." The wrapper changes but the feeling does not.
Our team is planning to launch a new version of our product on Product Hunt next week, after a period of optimization and improvements. As we get closer to launch day, I realize there s a lot to prepare, and I m curious about how other teams usually approach this process.
So far, here s what we ve been focusing on:
Most importantly, making sure the product works well and delivers real value
Continuous testing to ensure performance and stability
Designing clean and clear product screenshots
Preparing a summary of what s been updated, fixed, or optimized
Writing launch content (tagline, description, first comment, etc.)
Maintaining good health and a stable mindset for the launch
Expanding our network and connecting with other makers
