The short answer
For most products we build one app in Flutter or React Native and ship it to both the App Store and Google Play. That usually costs much less than building two separate native apps, and keeps both platforms in step. We recommend fully native apps only when the product depends on features or performance that cross-platform frameworks don't handle well.
Two apps our engineers worked on show the range:
- AirYoda, a social audio matchmaking app: iOS and Android apps launched in four weeks.
- KFC Pakistan: development efficiency went from 30% to about 80% after we joined their partner team to finish the app.
One codebase or two?
| Flutter | React Native | Native (Swift and Kotlin) |
|---|---|---|---|
Codebases | One for iOS and Android | One for iOS and Android | Two, one per platform |
Language | Dart | TypeScript, like your web app | Swift and Kotlin |
Best for | Consistent custom design on both platforms | Teams that already work in React | Heavy graphics, deep hardware use, platform-first features |
Team you need | Flutter engineers | React Native engineers | Separate iOS and Android engineers |
Our Flutter developers and React Native developers pages explain what we vet for in each.
What a launch-ready app needs
Features are what users see. These are what make an app survive its first month:
- Sign-in that works, including password resets and social login where it fits
- Push notifications and deep links that open the right screen
- Offline handling, so the app does something sensible on a bad connection
- Crash reporting and analytics, so you hear about problems before reviews do
- An API and backend the app can rely on, built and hosted alongside it
- Store listings, screenshots and privacy details for both stores
- Automated tests on the journeys that matter, which our QA automation engineers build
Store accounts and review
You publish under your own company's developer accounts, so the app belongs to you. Apple's Developer Program has an annual fee, and Google's Play Console has a one-time registration fee. We set up the builds, handle store review feedback, and manage release tracks for testing and launch.
Both stores review apps before they go live, and both have rules on payments, privacy and content. We check those rules against your plan at the scoping stage, so nothing in the design gets rejected at the end.
How we build it
- Scope call. Thirty minutes on who the app is for and what the first version must do. Free.
- Written plan. Screens, features, team, timeline and price in writing before work starts.
- Two-week sprints. A test build on your phone at the end of every sprint, and a Loud Report every Friday with what shipped and what is blocked.
- Launch and run. We ship to both stores, monitor crashes and reviews, and keep improving the app or hand it to your team.
Starting from scratch? Our MVP development guide covers what to cut from a first version. Building a subscription product? See SaaS development for the backend side.
What it costs
We price each app from a written plan. For scale, teams are built from the same roles and monthly prices on our public rate card:
Team | Good for | Monthly cost at our rates |
|---|---|---|
One senior mobile engineer | An app on an existing backend | $3,500 |
A senior mobile engineer and a senior backend engineer | A new app with its own API | $6,700 |
Product team: PM, design, engineering, QA | A larger app that we manage end to end | Custom, quoted in the plan |
Store fees, hosting and third-party services such as maps or payments are listed separately in the plan.