Wellness & Fitness App Development: UnVape
Wellness app development for a global fitness brand: UnVape, a cross-platform quit-vaping app, shipped production-ready on iOS, Android, and web from one codebase in a few weeks.
- Geography
- Germany
- Stage
- Established global fitness brand
- Team
- 1 senior + 1 mid full-stack engineer, 1 product designer, 1 product owner
- Duration
- A few weeks
The situation
Asana Rebel, the global fitness and wellbeing brand, needed a wellness app development company to ship a brand-new product. The new initiative, UnVape, would help users quit vaping through daily check-ins, progress tracking, and a habit-formation loop, and it had to feel like an Asana Rebel product from day one.
That set a high bar for an outside team. UnVape had to ship as an MVP at Asana Rebel's internal quality standard, live inside the existing engineering monorepo, cover iOS and Android from a single codebase, and include a web onboarding funnel to convert acquisition traffic. Just as important, the engagement had to end with a clean handover so the in-house team could own the app from launch onward.
What we built
Leanware staffed a four-person team (one senior full-stack engineer, one mid-level full-stack engineer, a product designer, and a product owner) and delivered the build as a fixed-scope AI Product Engineering engagement against milestones, running for a few weeks against the MVP spec.
One codebase, three surfaces
The mobile app shipped in React Native, targeting iOS and Android from a single codebase, the setup most buyers are weighing when they evaluate a cross platform app development company. The web onboarding funnel ran on Next.js and fed new sign-ups into the same Supabase backend the app reads from. Both surfaces share authentication, profile state, and progress data, so a user who starts in the web funnel lands in the mobile app without re-entering anything.
Working inside the client's monorepo
All work landed in Asana Rebel's existing GitHub monorepo. Code style, review cadence, and CI pipelines followed the host repo's conventions rather than a toolchain Leanware brought along. QA covered both platforms across a range of device sizes before handover, and the handover package included full documentation and a working CI/CD pipeline.
Outcome
-
MVP shipped within scope across iOS, Android, and web
-
Full handover documentation and CI/CD pipeline delivered to the in-house team
UnVape shipped as a production-ready cross-platform app on iOS, Android, and web, delivered within the MVP scope and against milestones. For a fitness brand extending into new wellness territory, the more durable result is what happened at handover: the in-house team picked the app up on day one with documentation, CI/CD, and everything needed to operate it already in place.
No business or user metrics are public for UnVape, so the outcome here is scoped to what the engagement was hired to do: ship the product at the brand's quality bar and leave the client's engineers fully in control. That is the test worth applying to any wellness app development company, not just whether the app shipped, but whether the client's own team could run it the next morning.
"They were responsive, clear in their communication, and delivered milestones on time."
— Dominique Plummeridge , Head of Engineering , Asana Rebel · Berlin, Germany
Engagement lines
Engagement FAQ
How much does it cost to develop a wellness app?
It depends on scope. UnVape was delivered as a fixed-scope, milestone-based build by a four-person team: a senior full-stack engineer, a mid-level full-stack engineer, a product designer, and a product owner. Cost scales with team composition and duration, so a scoped spec is the starting point for a real number.
How long does it take to build a fitness or wellness app MVP?
UnVape went from MVP spec to a production-ready app on iOS, Android, and web in a few weeks. Timelines depend on scope and integration requirements; building inside an existing monorepo, as this project did, adds conventions to follow but avoids rework later.
Can a wellness app share one codebase across iOS and Android?
Yes. UnVape uses React Native to target both platforms from a single codebase, with a Next.js web funnel feeding the same Supabase backend. Authentication, profile state, and progress data are shared, so users move between web and mobile without re-entering anything.
Can an outside development team work inside our existing codebase?
That was a core requirement of this engagement. Leanware's team worked inside Asana Rebel's GitHub monorepo and followed the host repo's code style, review cadence, and CI pipelines rather than bringing its own toolchain.
What does a fitness app development company hand over at the end of a build?
On this project, handover included full documentation and a working CI/CD pipeline, so Asana Rebel's in-house team had everything needed to operate the app from day one after launch.
What tech stack was used to build UnVape?
React Native for the iOS and Android app, Next.js for the web onboarding funnel, Supabase as the shared backend, GitHub Actions for CI/CD, and Figma for design.