MVP scope
A focused first release
← Back to all work
Mabrosi · Mobile product
From mobile MVP to daily habit
A mobile product foundation that connected onboarding, matching, safety, and re-engagement into one focused beta path.
THE BRIEF
The beta needed a clearer path from sign-up to a complete profile and a reason for dormant users to return.
The MVP problem
At Mabrosi, I was responsible for defining an iOS and Android MVP from customer requests, requirements, and market analysis. The product had several important flows - sign-up, matching, messaging, a conversation-style quiz, safety, and profile completion - but the first version needed a clear order of operations so the team could learn without turning the beta into a collection of disconnected features.
The user problem was visible after sign-up. People could enter the product without completing enough of their profile to receive useful matches, and dormant beta users needed a reason to return. I framed activation and re-engagement as connected product problems: users needed a simple first path, enough context for a relevant experience, and timely help when they paused.
The product decisions
I prioritized a focused MVP around activation, matching, messaging, the conversation-style quiz, and safety. That scope protected the core promise while giving the team a usable sequence to release and learn from. Progressive onboarding was designed to collect the information needed for matching without presenting the full burden of profile completion at once.
I also treated profile completion as a product behavior rather than a documentation problem. A complete profile was necessary for better matches, so the experience needed a clear explanation of why the step mattered. Re-engagement choices followed the same principle: prompts should point users to a next step, not simply announce that the app exists.
Carrying the work through
I used product analytics to inspect navigation, clicks, and time spent in the profile flow, then paired those signals with user surveys. The resulting plan included in-app nudges, email, push notifications, a start-where-you-left-off path, and a limited premium incentive for completing the profile. Each touchpoint had a clear job in the activation path.
Alongside the product flows, I defined and coordinated customer-facing foundations: the app guide, privacy policy, safety tips, quick start, FAQ, and community guidelines. These artifacts helped reduce ambiguity for users and gave the team a consistent explanation of the product as the beta evolved.
The outcome
The re-engagement program converted 20% of dormant beta users back to daily activity. The work also improved the product's ability to learn from activation behavior because it made the path from sign-up to profile completion more observable and more intentional.
The lesson is that mobile product delivery is not only about shipping the first screen. It is about deciding what a new user must understand, what the product must learn, how safety and trust show up in the flow, and which return path deserves investment before the team expands scope.
PRODUCT SYSTEM
Mobile product direction: connect a focused MVP to the activation path and a measured return loop.
Activation
Onboarding and early value
Return loop
Staged re-engagement learning
THE OUTCOME
dormant beta users returned to daily activity
WHAT STAYED WITH ME
“A mobile MVP earns momentum when its first-use path, safety model, and return loop are designed as one product.”
MORE TO EXPLORE
See all work ↗