Senior React Native developer for cross-platform mobile apps
Based in Wroclaw, Poland · EU timezone · Available for new projects
I build mobile apps with React Native and Expo that ship to both iOS and Android from a single codebase. From companion apps for existing web products to standalone mobile-first experiences — native performance without separate iOS and Android teams.
Companion mobile app
Mobile version of your existing web product. Shared authentication, synchronized data, push notifications, and offline access. Built to complement the web experience with mobile-specific features like camera, GPS, and biometrics.
MVP mobile app
Get to the App Store and Google Play fast. I build the core features, authentication, push notifications, and analytics in weeks. Iterate based on real user feedback instead of guessing at features.
Cross-platform from one codebase
Single TypeScript codebase producing native iOS and Android apps. Shared business logic, shared UI components, platform-specific adjustments where needed. Half the cost and maintenance of separate native teams.
App Store optimization and publishing
I handle the full publishing pipeline: app signing, store listings, screenshots, TestFlight and Google Play beta, and production release. Including OTA updates with Expo Updates for instant bug fixes without app review.
Performance optimization
Profiling and fixing jank, reducing bundle size, optimizing list rendering with FlashList, and minimizing bridge crossings. Native feel on mid-range devices, not just flagship phones.
Expo ecosystem
Expo Router for file-based navigation, EAS Build and Submit for CI/CD, Expo Updates for OTA delivery. I use managed workflow when possible and eject to bare workflow when native modules require it.
Native bridging
When React Native's built-in modules aren't enough: custom native modules, Turbo Modules for performance-critical paths, and integration with platform-specific SDKs (HealthKit, Google Maps, payment terminals).
Offline-first architecture
Local data persistence with WatermelonDB or MMKV, background sync, conflict resolution, and optimistic UI updates. Apps that work reliably in spotty network conditions.
Navigation and deep linking
Expo Router or React Navigation with proper deep linking, universal links (iOS) and app links (Android), and navigation state persistence across app restarts.
Push notifications
FCM and APNs integration via Expo Notifications or Notifee. Rich notifications, notification grouping, deep link handling, and in-app notification centers. Silent pushes for background data sync.
Testing on real devices
I test on real iOS and Android devices across multiple screen sizes and OS versions. Detox for E2E testing, Jest for unit tests, and manual QA on a device matrix that matches your user base.
Platform assessment
We define which platforms to target, which native features you need, and whether Expo managed workflow covers your requirements or we need bare workflow. No over-engineering — just the right tool for the job.
Build and test on devices
I build features and test on real devices from day one. Every sprint ends with a TestFlight/Play Store beta build you can install and test yourself. No simulator-only demos.
Publish and support
App Store and Google Play submission, OTA update pipeline, and crash monitoring. Post-launch, I can iterate on features or hand off the codebase with full documentation.
React Native is the right choice when you need both platforms, want to ship faster, and your app doesn't require heavy GPU work (3D games, AR). For most business apps, productivity tools, and social platforms, React Native delivers native performance at half the development cost.
Yes, Expo is my default starting point. It handles builds (EAS), OTA updates, and most native APIs out of the box. If a project needs custom native modules beyond what Expo supports, I eject to bare workflow — but that's rare with the modern Expo ecosystem.
Yes — that's the whole point. One TypeScript codebase, two native apps. I handle platform-specific differences (navigation patterns, permissions, UI conventions) so each platform feels native to its users.
I manage the full process: code signing, build configuration, store metadata, screenshots, TestFlight/Play Store beta testing, and production release. I also set up OTA updates so you can push bug fixes without waiting for app review.
Yes. I work with whatever API your backend exposes — REST, GraphQL, or WebSockets. If you have a web app and want a mobile companion, I'll integrate with the same authentication and data layer.
I work on a daily or monthly rate depending on the engagement. Book a free 30-minute call and I'll give you an honest estimate based on your app scope and timeline.
Ready to hire a senior React Native developer?
Book a free 30-minute technical call. I'll review your requirements and tell you honestly if I'm the right fit.