Services
Mobile engineering, from the first plan to the store release
For founders and product teams who need a mobile app built, rescued or moved to shared code. Remote worldwide from Gurugram (IST), and on-site in Delhi NCR. I keep a few hours of overlap with European and US mornings.
Working with a team in India? Rupees, IST and Delhi NCR →
MVP build
Take an idea to an app in the store. Native Android, Kotlin Multiplatform or React Native, chosen for your product and team rather than my preference.
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
Offline-first apps
Apps that keep working with no signal and never lose what people entered: the phone as the source of truth, and sync designed with your backend team rather than bolted on.
What's included
- A data model with the device as the source of truth
- A sync contract agreed with your backend team
- Background upload queues for photos and files
- Conflict handling and sync status people can see
App rescue and modernisation
For apps that have become hard to change or release. Stabilise first, then modernise in steps you can ship.
What's included
- Codebase and release-process audit
- Architecture plan with an incremental migration path
- Compose migration, dependency and SDK upgrades
- CI/CD with GitHub Actions and Fastlane
Kotlin Multiplatform migration
Start sharing code between Android and iOS with a Kotlin Multiplatform data layer, the way HelperBook does, then grow it one module at a time.
What's included
- Deciding what to share and what stays native
- Shared module design with a SQLDelight data layer
- Incremental adoption alongside your existing apps
- Build setup for the shared module in your existing release process
Fractional mobile lead
Part-time ownership of your mobile side when you need senior judgement but not a full-time hire yet.
What's included
- Architecture and technology decisions
- Release process and quality bar
- Code reviews and working with your backend and web teams
- Helping you hire your first mobile engineers
How it works
Four steps, no surprises
01
Discovery
A short, paid sprint to understand the product, the code (if any) and the constraints. You get a written plan and estimate you can use with anyone.
02
Build in short cycles
Working builds on a test track every week or two, so you see progress on a real phone, not in slides.
03
Release
Signing, store listings, Data Safety and a staged rollout on Google Play and the App Store.
04
Handover
The code transferred to your repository at each paid milestone, CI in place and the decisions written down, so your team can take over.
Ways to work together
Start small, then choose what fits
Start here
Paid discovery
A fixed fee of ₹60,000 (US$900) for about a week: audit or product scoping, ending in a plan and estimate.
Fixed-scope project
An agreed scope, timeline and price. Best when the first release is well defined.
Time and materials
Billed by the day or week against a plan. Best for rescues where the scope becomes clear as we go.
Monthly retainer
A set number of days each month, for ongoing work or as your fractional mobile lead.
FAQ
Questions clients ask
Do you work remotely?
Yes. Remote worldwide from Gurugram (IST), and on-site in Delhi NCR. I keep a few hours of overlap with European and US mornings.
Native, Kotlin Multiplatform or React Native?
I have shipped all three in production: native Android and iOS apps, a shared Kotlin Multiplatform module in HelperBook, and a full React Native rewrite of the Pulse apps. I recommend one based on your team, timeline and which parts must be native.
Can you work with our existing team?
Yes. At Pulse I designed the sync contract with the backend and web teams and led the React Native rewrite alongside the team.
Do you handle the Play Store and App Store release?
Yes: signing, R8, Play Data Safety declarations, store listings and staged rollouts. I have shipped apps to both stores.
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.
Is there anything you don’t take on?
Games, and crypto or gambling products. Everything else with a mobile app at its core is worth a conversation.
How do we start?
Usually with a paid discovery sprint. It gives you a written plan and estimate, and gives us both a low-risk way to see if we work well together.