MVP Scope & Design Constraints
We kicked off the project in early 2024 and aimed to launch right after Q2. That gave us just 3 months to go from design to ship.
Under a tight deadline, we focused our MVP on iOS — where most of our paying subscribers were. This gave us the best chance to gain traction quickly and validate the concept early.
We launched the MVP in June 2024, gathered insights from real users, and immediately began refining the experience. Over the next few months, we iterated rapidly before expanding to Web and Android.
For the early user flow, we created a single, unified flow for both free and paid users — selecting a pack, uploading a photo, confirming, and viewing a single-image preview that acted as a soft gate before the experience branched. From there, free users reached the paywall, while subscribers regenerated to see their full results.
This wasn’t the most elegant UX. Subscribers went through the generating screen twice, which made the experience feel heavier and repetitive.
However, this was a deliberate, business-first decision. A shared flow made the experience faster and simpler to build under tight time and resource constraints. The preview before the paywall created a clear “moment of proof,” letting users see the AI working and helping build trust and drive conversion.
The flow met our initial business goals, but it also revealed opportunities to improve usability. After launch, we revisited the flow to make the experience lighter and smoother.
Early User Flow