Building production mobile apps with React Native & Expo
React Native done well gives you one codebase, two native apps, and real hardware access — without a compromise on quality. I have shipped mobile products to the App Store and Play Store across fintech, travel, health and networking, with the parts that usually go wrong (payments, provisioning, offline) done properly.
One codebase, genuinely native features
On Expo/React Native I have built NFC/QR digital business cards (Cardly), an eSIM app with QR / one-tap provisioning (AloAlo), an AI product-scanner (Sumus) and health apps — using Expo Router, TanStack Query, react-hook-form and Zod, plus native modules where the platform demands it. The result feels native because the hard integrations are native.
Payments, auth and offline that hold up
The failure points in mobile are rarely the UI. I wire Stripe and RevenueCat subscriptions, Supabase/NestJS backends, secure auth and offline-first data so the app keeps working on a bad connection and money flows reliably. Weekly production releases keep the loop tight.
AI on the phone, backend behind it
Because I also build the backend and the AI, mobile features that depend on a server — scan-to-insight, LLM chat, personalised recommendations — come together as one system instead of three teams negotiating an API. That is how Sumus’ scan-and-score and Ealthiness’ AI meal analysis shipped.
- Native iOS + Android from a single Expo/React Native codebase.
- Payments (Stripe/RevenueCat), secure auth and offline-first done right.
- Mobile, backend and AI built together as one coherent product.