Service · 03 · Mobile
An app in the stores, talking to a real backend — not a wrapper around a website.
Cross-platform apps with React Native and Expo, plus the API, auth, and data the app has to call. We build first products and companion apps for teams that already have a web platform.
Two paths. Same studio. Pick the one that matches — both are in scope.
Path A · New app
One codebase, designed and built with the API it needs to live — not a wrapper around a website.
Path B · Companion
We sit on your existing API or extend it, then ship the mobile surface your users actually open.
The product shapes inside this service, in plain terms.
One product on iOS and Android. Native modules where the OS will not negotiate.
Auth, push, media, and the endpoints the screens require — we do not hand you a UI over a missing backend.
Build, signing, and a release cut you can submit. Listing copy is on you unless you ask.
Crash fixes, OS updates, and the next features — same studio, not a new vendor.
What you can expect in scope when this is the brief.
UX/UI for the mobile flows in scope
React Native app for iOS and Android
API work or integration with what you already run
A build you can put on TestFlight / Play internal testing
The atlas currently shows live web products. Mobile work uses the same studio — React, Node, and a launch path. Ask for app briefs in the form.
A studio cut, not a staff-aug black box.
What the app must do offline, logged-in, and on a bad network.
Mobile UI and the API contract behind each screen.
App, backend slice, device testing.
Internal builds, then store submission support.
Flows → app → API → release
Straight answers. The rest belongs in the brief.
React Native / Expo when one product should cover both stores. Native modules for the pieces the OS owns. Full native is a different brief — say so up front.
Yes, or we connect to yours. An app without auth, data, and a release API is a demo.
Yes. Companion apps against a live API are a common brief. We extend the API if the app needs more than the website exposes.
The public atlas is web products we can show. Mobile work follows the same process. If you need a confidential walkthrough, say so in the brief.
Same studio. Different job.
Field intake
This form is already tagged for mobile app development.