011–2 weeks
Scope and platform choice
Feature list, offline and notification needs, and the native-or-cross-platform decision with reasons.
Mobile App Launch
An app in the App Store and Play Store, with a backend, a release pipeline, and the review process handled, in three to six months.
The buyer question this answers: Can you take an app end to end, including the stores?
Who this is for
- A web product whose users want it on their phones.
- A field team that needs to work offline and sync later.
- A consumer idea that only makes sense with notifications and the camera.
Phase by phase
Reference timings for a typical engagement. The written scope gives you the dates for yours.
- 022–3 weeks
Design and architecture
Screen flows, the API contract, offline strategy, and developer accounts in your name.
- 038–12 weeks
Build
Weekly builds to your phone through TestFlight and internal testing, with a demo of what changed.
- 042 weeks
Hardening
Device testing, performance on older phones, crash reporting, accessibility, and store compliance.
- 051–2 weeks
Store submission
Listings, screenshots, privacy declarations, submission, and review feedback handled.
- 0630 days
Support window
Fixes on anything we built, and a documented pipeline for the next release.
The stack for this workflow
- Swift and SwiftUI
- Kotlin and Jetpack Compose
- React Native or Flutter
- Node.js or Python API
- PostgreSQL
- Firebase Cloud Messaging and APNs
- Fastlane
- GitHub Actions
- Sentry
What could go wrong
Every build has risks. These are the ones we plan for on this kind of project, and what we do about each.
Store review rejects the app.
How we handle itCompliance is checked in hardening, and the schedule includes one round of review feedback. Rejections are usually fixed in days.
Offline sync creates conflicts.
How we handle itThe sync strategy is designed in architecture, not discovered in testing, and conflict rules are written down.
The app is slow on the phones your users actually have.
How we handle itTesting on mid-range and older devices is part of every weekly build, not just the final one.
Cost model: Fixed scope
A first release is a defined thing. The scope phase makes it precise enough to price and date.
No prices on this page. The scope phase ends with a written quote for your project.
Questions we get asked
Native or cross-platform?
Cross-platform for most business and consumer apps, native when the app relies on platform features or performance. We recommend one in the scope, with reasons.
Do we need both stores on day one?
Not always. Launching on one platform first is a valid way to learn faster, and the scope can be staged that way.
Who owns the developer accounts?
You do. They are created in your name in the first phase so the apps are yours in the stores.
What happens after launch?
Thirty days of fixes are included. After that, your team can ship with the documented pipeline, or a retainer keeps the app current with OS releases.
Tell us what you are building.
We reply within one business day with how we would build it, what it would cost, and which engagement model fits.
- 01Tell us what you are building
A short form or an email. No deck required, and "not sure yet" is a fine answer.
- 02A call with an engineer
Within one business day. Technical questions get technical answers, from the person who would build it.
- 03A written scope and quote
Fixed price where the scope is defined. The document is yours whether or not you go ahead.