Loading...
Loading...
Mobile is dominated by three viable paths: native iOS (Swift / SwiftUI), native Android (Kotlin / Compose), and cross-platform (React Native + Expo, or Flutter). This roadmap covers the cross-platform path the fastest way to ship to both stores.
The non-mobile foundation
React Native is React with native primitives. The same hooks, the same component model, the same TypeScript. If React feels solid, you're 60% of the way there.
The default cross-platform stack
Expo is now the recommended way to do React Native. EAS Build handles signing, OTA updates handle hot fixes, and the docs are excellent. Plain React Native CLI is rarely necessary in 2026.
Expo Router, Zustand, React Query
Mobile UX lives or dies by smooth navigation. Expo Router (file-based, like Next.js) is the modern default. Pair with Zustand for local state and React Query for server state.
Push, deep links, offline, biometrics
These are the features that make a mobile app feel native: push notifications via Expo Notifications + a service like OneSignal, deep links to specific screens, offline storage with WatermelonDB or MMKV, biometric login.
Profiling, Hermes, occasionally Swift / Kotlin
When pure JS isn't enough, you write native modules. With Expo Modules in 2026 this is much friendlier than it used to be. Use Flipper or Reactotron to profile.
App Store, Play Store, TestFlight
Shipping to the stores is its own skill. Privacy manifests, review timelines, in-app purchases via RevenueCat, screenshot generation. Plan a week per launch.
On-device + API hybrid
AI features in mobile work best as a hybrid: small on-device models for low-latency interactions, plus API calls to frontier models for hard work. Apple's MLX and Google's Gemini Nano make on-device increasingly practical.
We pair these roadmaps with hands-on engagements pair-programming, code review, and architecture support.