Mobile apps
iOS and Android apps, from the first test build to the store, with crashes watched after every release and your team able to keep shipping after us.
- PlatformsiOS and Android
- Built withReact Native, or native
- After launchCrashes tracked per release
How a mobile release ships
Every release goes to testers first, then to users a few at a time.
Built in CI
Both platforms built from the same commit, signed and numbered automatically.
Test builds
Your team tries each version through TestFlight and Google Play testing.
Store review
We prepare the listing and answer the reviewers, with your accounts.
Staged rollout
A small share of users first, then everyone, with crashes watched throughout.
What we handle
The parts that make a mobile app feel finished.
- Offline use
The app keeps working without signal and syncs when it is back.
- Notifications
Push messages people asked for, sent at the right time, easy to turn off.
- Payments
In-app purchases and subscriptions, set up the way the stores require.
- Accessibility
Screen readers, large text and contrast on both platforms.
React Native or native?
We recommend one on the consult. These are the usual reasons.
- Most appsReact Native: one codebase for both
- Heavy graphics, AR, real-time audioNative, per platform
- You already have a native appWe keep it native
- Your team writes ReactReact Native, so they can own it
Questions about mobile apps
What usually comes up on the consult.
Whose store accounts are used?
Yours. The app is published under your Apple and Google developer accounts, so you own the listing and the reviews.
How long does store review take?
Usually a day or two. We plan releases around it, and test builds go out to your team in minutes.
Do we need a backend too?
Usually, for accounts, data and notifications. We build it as one API that your web app can share.
Can you take over our existing app?
Yes. The first week is a written review: what to keep, what to fix first, and what it would cost.