Services/Mobile Apps
Native-feel apps from a codebase you actually own.
A real mobile app — not a wrapped website. We build with React Native and Expo so iOS and Android share business logic, ship from one team, and stay in sync. Native-feel interactions, real offline support, and a path to the App Store and Play Store.
Ships with Properties — our runtime control plane for store URLs, feature flags, kill switch, and per-site analytics.
Who this is for
Three kinds of teams we work with.
SaaS adding mobile
Your web product is loved. Customers want it on their phone. We build the companion app without rebuilding the backend.
Retail and services going digital-first
Loyalty, bookings, ordering, member portals — the things your customers genuinely use on mobile.
Startups testing PMF
You need to put a real app in beta testers’ hands fast. We ship to TestFlight in week three.
What you get
Concrete deliverables. No vapourware.
The list below is what ships, not what we promise. Every project is quoted against this scope so you know exactly what you are paying for.
iOS + Android build
One codebase, two stores, shared business logic.
Native-feel UI
Platform conventions where they matter — your brand where it counts.
Offline support
Real offline mutations, queued sync, conflict handling.
Push notifications
Expo Push, segmented, actionable.
Auth + biometrics
Sign in with Apple, Google, email, plus FaceID / TouchID.
Backend sync
Shared API with your web app — one source of truth.
Crash + analytics
Sentry, analytics events, session replay.
Store submission
We handle TestFlight, Play Console, store assets, the lot.
Properties for app surfaces
Remote-control App Store / Play Store URLs, kill switch, feature flags via Properties.
How we do it
A four-step path. Designed not to surprise you.
Scope + design
We define the v1 scope ruthlessly. Mobile rewards focus.
Build in Expo
OTA updates from week one. Internal builds via TestFlight and Play internal track.
Beta + feedback
A real beta cohort uses the app for two weeks. We fix what they hit.
Store submission
Listings written, screenshots produced, review responses handled.
Stack
Selected work
See it in production.
Includes
- check_circleSingle React Native codebase
- check_circleiOS + Android builds
- check_circlePush, auth, offline support
- check_circleStore submission for both platforms
- check_circle60-day post-launch support
FAQ
Questions about mobile apps.
Everything we get asked at the start of a project. If yours is not here, just write to us.
For 90% of apps the user-facing difference is invisible — and you save half the cost and ship to both platforms simultaneously. When a project genuinely needs native modules, we write them. We are not religious about the framework.
Yes. We handle the developer accounts (or use yours), the listings, the screenshots, the privacy declarations, and the review process. Apple rejections are part of the job.
Almost always, yes. The same Next.js API or Firestore that powers your web app powers the mobile app. One source of truth.
We treat offline as a first-class state, not an afterthought. Reads cache, writes queue, conflicts resolve. You design for the bad-signal user from day one.
Most JS-only changes ship via Expo OTA without a store review — usually within minutes. Native changes go through normal store review.
Yes. One number, both stores. Going native-only would not be cheaper on one platform once you account for the lost reach.
Yes. Mobile design is its own discipline — we design the app from scratch in Figma before we write a line of code.
Related insights
Further reading from the workshop.
Practical writing on the topics this service touches — pricing, decision frameworks, ROI data, and the things that change once a project is live.