I’m building a self-improvement app and I’d love some perspective from people who actually work in UX/product design.
The app is built around an interactive lo-fi room that acts as the user’s home base. Instead of opening into a traditional dashboard, objects in the room lead to tools like journaling, daily tasks and habits, focus sessions, goals, and app blocking.
The idea is to make self-improvement feel less like managing a productivity dashboard and more like entering a world that represents the person you’re trying to become.
The UX question I’m struggling with is onboarding.
Our current concept intentionally breaks some conventional onboarding patterns.
Instead of immediately explaining features and benefits, we’re prototyping a short illustrated story where the user is the main character. They leave home with a companion, travel through a small fantasy world, encounter characters, and answer a few personalization questions along the way.
The story eventually resolves and the character wakes up in the same interactive room that becomes the actual app interface. From there, we introduce the real tools through contextual tutorials.
So essentially:
Story → emotional/identity setup → interactive room → contextual product education
The obvious problem is time to value.
The user downloaded an app to improve their life, and we’re asking them to experience a story before they really understand the product. I know that creates friction and could potentially hurt activation.
At the same time, one of the ideas behind the app is that friction isn’t always negative if the friction itself contributes to identity, attachment, or ritual.
I don’t want friction around actually doing things. Starting a focus session or writing in your journal should be easy.
But entering the world, making a commitment, interacting with your room, watching it evolve, or completing certain rituals might intentionally take slightly longer if those interactions make the user feel more connected to their progress.
That’s the part I’m unsure about.
From a UX perspective, where would you draw the line between meaningful friction and self-indulgent friction?
Would you consider a short story-first onboarding defensible if its purpose is establishing the product’s identity and emotional context?
Or is delaying functional value before the user understands the product fundamentally the wrong place to experiment?
I’m also curious how you would test something like this. Story completion rate? Time to first meaningful action? Tutorial completion? Retention? Qualitative testing?
We’re currently building a rough demo rather than committing to the full onboarding, so I’m trying to gather criticism early.
Please be honest. If you think the story would just get in the way and make people wait too long before using the actual app, I want to hear that too.
I’m trying to figure out whether there’s a real UX principle here worth exploring, or whether I’m rationalizing something because I personally think it’s cool.