The web app works. The mobile version has been three weeks from done for two months.
Mobile
Mobile development for apps that have to ship.
React Native and Expo, one codebase and two stores, with native code written where the bridge is not enough. We build apps that hold up on a four-year-old Android as well as they do on the demo device.
- commit
- native build
- test build
- store review
- staged rollout
- someone's phone
Every stage is part of the engagement, not a separate invoice.
You are probably here because
If none of these sound like your app, the free call is still the fastest way to find out what does.
The prototype runs in Expo Go and nowhere else, and the first real build fails.
It ships, but the crash-free rate is a number nobody wants to say out loud.
Nobody on the team has taken an app through store review before, and launch has a date.
The AI feature works in the web version, and nobody has made it work on a phone.
What the build covers
Fixed scope, fixed price, agreed before anyone writes code. If something outside this turns out to matter more, we re-scope in the open instead of quietly billing for it.
- Architecture
- Navigation, state, and data layer picked for the app you are actually building. Typed end to end, so a rename fails at build time instead of in a review queue.
- AI surface
- Streaming that survives a dropped connection, the model call moved off the device so the API key does not ship in the bundle, per-user token cost you can see before the invoice does, a fallback for when the provider is down, and the moderation and disclosure the store reviewer will ask about.
- Native surface
- Camera, push, background tasks, deep links, biometrics, in-app purchases. Wired to the platform APIs directly, not to a wrapper that breaks at the next OS release.
- Builds
- EAS, or bare Xcode and Gradle, reproducible on CI and signed with credentials that stay in your account.
- Release
- TestFlight and the internal track, store listings, review submission, staged rollout, and over-the-air updates only where they are safe to use.
- Observability
- Sentry, crash-free rate, and release health per version, so a bad build is visible to you before it is visible in the reviews.
- Tests
- Unit and integration tests on the logic that is expensive to get wrong, and Detox end-to-end runs of the critical flows, driven from EAS Workflows so they execute on CI against a real build rather than on somebody's laptop. We use AI to generate the cases nobody sits down and writes: the interrupted call, the killed background task, the dropped network mid-upload, the back gesture at the wrong moment. A senior engineer decides which of them are real, because most are not.
- Handoff
- Repo, runbook, credentials, and a walkthrough. You can hire anyone to take it from there, including not us.
Price
One number, agreed before we start.
A build from an idea rather than an existing app is the AI MVP scope, up to $12,000 over four weeks. Smaller pieces start at Audit & Fix.
We have shipped our own products to real users: Mira on the iOS App Store and ariex.fit in public beta. There are no rescue case studies in the portfolio yet, and we are not going to claim there are some under NDA.
Mobile
Production-Ready
React Native and Expo, through native code and store review.
Start with the free callGo deeper on one part.
Same team and the same fixed-price shape, scoped to a single problem instead of a whole build.
Expo & EAS
Config plugins, EAS builds, and OTA updates you can roll back.
Native modules
Swift and Kotlin on one side, your JavaScript on the other.
App Store rejection
The guideline read, the cause fixed, the reply written.
Questions we get asked first.
Anything not answered here is worth twenty minutes on a call.
How much does a React Native app cost?
A production-ready build of a focused app is up to $7,500 over three weeks. An audit and fix of an existing app is up to $1,800, with the fix list in your hands in two days. A product built from an idea is the AI MVP scope, up to $12,000 over four weeks. An app with a large feature surface costs more, and we scope it on the call rather than guessing a number here.
React Native, or native Swift and Kotlin?
React Native for most products: one team, one codebase, and the platform gaps closed with native modules where they matter. Native when the app is built around something the bridge is bad at, like heavy real-time audio, video processing, or a watch app. We have shipped both. If native is the honest answer for your app, we will say so on the call.
Can you take over an existing React Native codebase?
Yes, and that is most of what we do. It starts as an audit, and two working days later both sides know what is actually in there before anyone commits to three weeks of work.
Do you submit to the App Store and Play Store for us?
Yes. Listing metadata, screenshots, privacy manifest, data safety form, review submission, and the back-and-forth with App Review if there is any. The developer accounts stay yours.
How long until the first build is on my phone?
Usually the first week. Getting a signed build onto real devices early is the point, because that is where the problems the simulator hides show up.
Book the audit
Want a straight answer on this one?
Send the repo, the rejection notice, or just the idea. Twenty minutes is enough to tell you whether a rescue, a rebuild, or a clean no is the right next step.
Prefer email? [email protected]