MVP build
Your startup’s MVP app, from the first plan to the store
I take startup apps from an idea to a release in the store: scoping the first version with you, choosing the stack for your product and team, building it, and handling the release. I’ve owned four greenfield Android builds end to end.
Opens Cal.com in a new tab.
- greenfield Android builds, owned end to end
- 4
- screens built from concept to production release
- 30+
- B2B clients on an app I took from early prototype
- 100+
- years building Android and iOS apps
- 13
Who it’s for
Sounds familiar?
- You have a product idea and a deadline, but no mobile engineer yet.
- You need to decide what the first release must do, and what can wait.
- You’re not sure whether to go native, Kotlin Multiplatform or React Native.
- You want an app your own team can take over later, not one only its builder understands.
How I build it
How I take an MVP to the store
01
Scope the first release
We agree what the first version must do and what can wait, in a paid discovery sprint that ends in a written plan and estimate you can use with anyone.
02
Choose the stack for your product
Native Android, Kotlin Multiplatform or React Native, chosen for your product, team and timeline rather than my preference. I’ve shipped all three to production.
03
An architecture that outlives the MVP
For a video-first hiring platform I built 100% of the Android client, 30+ screens across candidate and recruiter flows, on a modular Compose, MVVM, Hilt and Flow codebase the app still runs on.
04
Working builds every week or two
You get builds on a test track as the app grows, so you see progress on a real phone, not in slides.
05
A release you can trust
Signing, R8, Play Data Safety declarations, crash reporting with no personal data in it, and a staged rollout. HelperBook went from its first commit to a public release on Google Play this way.
What you get
What’s included
- Scoping the first release with you
- Architecture and data model, offline-first where it matters
- The app itself, in Jetpack Compose or your chosen stack
- A simple backend when you need one, in Firebase or Django
- Store release: signing, Data Safety, staged rollout
How we start
Paid discovery
A fixed fee of ₹60,000 (US$900) for about a week: audit or product scoping, ending in a plan and estimate.
FAQ
Questions clients ask
What does an MVP cost?
Every MVP starts with a paid discovery sprint: a fixed ₹60,000 (US$900) for about a week. It ends in a written plan and an estimate for the build, which you can use with me or anyone else.
Android, iOS or both?
Whatever your users need first. I’ve shipped native Android and iOS apps, a shared Kotlin Multiplatform data layer and a React Native app, so the choice follows your product rather than what I know.
Do you build the backend too?
When the MVP needs a simple one, yes: I’ve shipped backends on Firebase and Django. For bigger systems I work with your backend team from an agreed API contract, as I did at Pulse.
Who owns the code?
You do, once each milestone is paid. I work in my repository, give you read access from the start so you can see every commit, and transfer the code to yours at each paid milestone.
Tell me about the app you want to launch
Tell me what exists today and what you need by when.