Mobile apps
We build cross-platform mobile apps with React Native or Flutter, so you ship to iOS and Android without paying for two separate teams. We also handle store submission, push notifications, analytics and the back end the app depends on.
What is included
iOS and Android apps from one codebase, published and maintained.
- Cross-platform build
- One codebase for iOS and Android, with native modules where performance needs them.
- App store publishing
- Store listings, review submissions and release management under your developer accounts.
- Back end and sync
- APIs, offline support, push notifications and user accounts.
- Analytics and crash reporting
- See what users do and what breaks, from the first release.
How it works
From first call to launch.
Discovery
We map what the software must do, who uses it and what it connects to.
Scope and estimate
A written scope, milestones and cost, agreed before development starts.
Build in sprints
Two-week cycles, each ending with a working demo you can click through.
Launch and support
Deployment, monitoring, and either a clean handover or ongoing maintenance.
What a typical project looks like
A typical mobile project is a consumer or field-team app that needs offline access, push notifications or the camera. Many start with an existing web product that users now want on their phones.
We design the key screens first, then build one React Native or Flutter codebase for iOS and Android. The back end, analytics and crash reporting are set up from the first sprint, and we handle TestFlight, Play Console testing and store review. A first release usually ships in ten to sixteen weeks.
Timeline
Typical timelines. You get a fixed written estimate after scoping, before any work starts.
- App on top of an existing back end
- Eight to twelve weeks.
- App with a new back end
- Twelve to sixteen weeks.
- Maintenance
- OS updates, fixes and small features on a monthly plan after launch.
A good fit if
- Your users spend more time on their phones than on a laptop.
- You need offline access, device features or push notifications.
- You want both platforms without doubling the budget.
Questions
Native or cross-platform?
For most startup apps, cross-platform is faster and cheaper, and users will not notice the difference. We recommend native only when the app leans heavily on device hardware.
Will you publish the app for us?
Yes, under your own developer accounts, so the listing, ratings and reviews stay yours.
What happens after launch?
We offer ongoing maintenance for OS updates, fixes and new features, or a clean handover to your team.
How much does it cost to build a mobile app?
It depends on whether a back end already exists and how much the app relies on device features. You get a fixed written estimate after scoping.
Should we build a web app or a mobile app first?
If your users work at a desk or buy through a browser, start with the web. If they need the product in the field, offline or with notifications, start with mobile. Our guide on the question goes into detail.
Further reading
- Guide
Web app or mobile app: which should your startup build first?
How to decide whether your startup should build a web app or a mobile app first, based on your users, your budget and what your first version has to prove.
- Blog
How much does it cost to build an MVP?
What actually drives the cost of a startup MVP, how to estimate it before you talk to a development team, and where founders tend to overspend.
- Blog
Seven questions to ask a development team before you sign
What to ask an outsourced software team so you know what you are buying before the contract is signed.
Have something to build?
Tell us what you are working on. We will come back with questions, not a sales script.