Ex-Disney · Ex-Globant · Freelance since 2014
Hire a senior React Native developer who ships apps users keep.
I build React Native apps that make it past App Review, survive production, and feel native on both iOS and Android. Real-time chat, payments, AI verification, store submissions — end-to-end, not just a starter template.
Start a projectOne codebase, two platforms done right
Shared TypeScript everywhere — with platform-specific tweaks where iOS and Android expect to feel different. Not a lowest-common-denominator app.
Native modules when it matters
I write Swift or Kotlin when React Native isn't enough — HealthKit, Bluetooth, custom camera flows, biometrics. No hand-waving around "mobile limitations".
Ships to the stores, not just TestFlight
App Review rejections, privacy manifests, crash rates, OTA updates, store screenshots, release tracks — I've handled the full submission and post-launch cycle.
Performance you can feel
Reanimated for 60fps animations, FlashList for long lists, Hermes for startup time, lazy routes — the app feels fast because it is.
The React Native stack I ship with
- React NativeCore framework — the New Architecture when the project justifies it
- ExpoBare or managed — I pick based on what the app actually needs
- TypeScriptStrict types across screens, services and native bridges
- iOSSwift modules, privacy manifests, Apple Sign In, universal links
- AndroidKotlin modules, deep links, permissions, Play Integrity
- Redux ToolkitPredictable state for complex multi-screen flows
- React QueryServer state and caching — stale-while-revalidate done right
- ReanimatedNative-thread 60fps animations without JS bridge overhead
- FirebaseAuth, Firestore, Cloud Messaging, Remote Config, Analytics
- StripeIn-app payments with Apple Pay and Google Pay
- SentryProduction crash reporting, performance traces, release health
- DetoxEnd-to-end testing so releases don't break silently
When React Native is the right call
React Native makes sense when you want one team shipping both iOS and Android without writing the app twice. It's boring-in-a-good-way technology now — Meta, Shopify, Microsoft and Coinbase all use it in production. That said, it's not the universal answer.
Choose React Native when the app is mostly UI, API calls, standard device features (camera, push, payments) and you want the same engineer owning web and mobile too. Expo's managed workflow fits startups and MVPs that don't need exotic native modules. Bare React Native fits when you know you'll ship custom native code from day one.
Skip React Native when the app is built around a single heavy native subsystem — ARKit-first AR experiences, pro audio apps, games, or anything needing fine-grained Metal/Vulkan. Native Swift or Kotlin wins there. Flutter is also reasonable for apps with heavy custom UI and no web companion — but the ecosystem is smaller and hiring is harder.
I've shipped React Native apps used by travelers across 28 countries (Greether), internal tools for tourism operators (Argenway), and healthcare-adjacent mobile layers. Each one had a different balance of shared-vs-native code, and each shipped to both stores without drama. The value of React Native isn't "write once, run anywhere" — it's "share 80% of the work, keep the 20% that makes the app feel right per platform".
FAQs
Yes. I've shipped to both stores with equivalent polish. iOS gets more pixel-perfect attention because the audience often demands it, but Android is never an afterthought — permission flows, Material Design patterns and Play Console submissions are covered.
Start with Expo managed. Eject only when you hit a real native module limitation. I've migrated Expo apps to bare when needed (usually around custom Bluetooth or a specific native SDK) — it's a one-week project, not a rewrite.
Handled it dozens of times. Privacy manifests, in-app purchase requirements, restricted entitlements, metadata rejections — all part of the work. I'll flag risky choices before you build, not after the rejection.
Both. Most recent work is adding features to existing codebases — audits, performance fixes, migrating to the New Architecture, adding native modules. I'll read the code before quoting.
Standard kit. FCM/APNs for push, Stripe or Apple IAP for payments, RevenueCat for subscriptions, Mixpanel or Amplitude for analytics, Sentry for crash reporting. I'll pick based on your stack, not my preferences.
Fixed-scope for MVPs. Weekly retainer for ongoing feature work. Hourly for small fixes or audits. I don't pad hours — if something takes less than the estimate, I pass the saving.
Need a React Native engineer who ships apps users keep?
MVPs, feature work on existing apps, store submissions, performance audits. Reply within 24 hours.
Start the conversation