12 weeks. iOS and Android. Production-ready. Not a prototype.
React Native with Expo gives you a single codebase for both stores, with production performance and native access to the device features you actually need. The 12-week timeline is real — for a defined scope. Fixed scope, fixed price.
You need to ship a mobile app in 12 weeks — for a product launch, an investor milestone, or a customer commitment — and you need it to work on both iOS and Android.
The two timelines that kill mobile app projects: the native iOS/Android approach that requires two separate codebases (24 weeks minimum to ship both stores with two developers, $80k–$120k before a single user downloads the app); and the React Native project that was scoped as a 12-week project but took 24 weeks because the scope wasn't defined precisely enough before development started.
React Native with Expo solves the first problem — one codebase, both stores, one developer, 12-week timeline for a defined scope. The second problem — scope drift turning a 12-week project into a 24-week project — is solved by the fixed-scope model. The spec is the contract. Development starts when the spec is approved. Changes to scope after approval are change orders with explicit timeline and cost impact.
The React Native architecture questions that determine the timeline: is there an existing backend the mobile app connects to, or does the backend need to be built from scratch? (Backend + mobile = 16–20 weeks; mobile connecting to existing backend = 10–14 weeks.) What native device features are required? Camera, location, notifications, biometric authentication, Bluetooth — each adds to the complexity. What is the offline behaviour requirement? Full offline capability is a significant architecture investment; notifications-when-connected-only is much simpler.
A production React Native app with Expo, deployed to both the App Store and Google Play, with the core feature set, push notifications, and the backend infrastructure to support real users.
Expo managed workflow
EAS Build for both App Store and Google Play submission. Expo's managed workflow handles the native build infrastructure, reducing the deployment complexity to a configured build pipeline rather than a full Xcode and Android Studio setup. Over-the-air updates for JS changes that don't require native builds.
Authentication with Clerk
Clerk Expo SDK for cross-platform auth — email/password, magic link, and social OAuth. Biometric authentication using the existing Clerk session. Token refresh handled automatically.
Push notifications with Expo Notifications
Push notifications via Expo's push notification service, with notification handling in foreground and background, deep linking from notification to screen, and notification preference management in the user account settings.
Core feature set
The 4–6 screens and the workflows behind them that deliver the core value of the application. Designed mobile-first — not a responsive web UI ported to mobile, but the native mobile UX that matches user expectations on iOS and Android.
App Store submission
Both App Store (Apple) and Google Play (Google) submissions, including metadata, screenshots, and the review process management. The app live in both stores.
One honest number to start.
Fixed-scope, fixed-price. The number below is the starting point — final scope is built from your brief.
A production React Native app with Expo, deployed to both the App Store and Google Play, with the core feature set, push notifications, and the backend infrastructure to support real users.
Three steps, every time.
The same repeatable engagement on every project. No surprises, no mystery, no billable ambiguity.
Brief & discovery.
We send you questions, then get on a call. Output: a written scope with every step, feature, and integration listed.
Build & ship.
Fixed schedule, weekly reviews. No scope creep unless you change the scope — and if you do, we reprice it transparently.
Warranty & retainer.
30-day warranty on every launch. Most clients stay on a monthly retainer for ongoing features and maintenance.
Why Fixed-Price Matters Here
App Store review timelines (Apple: 24–48 hours) add a variable at the end of the project that can slip a launch. The project timeline accounts for this. Fixed scope, fixed price.
Related engagements.
Questions, answered.
Yes — for mobile apps that require a new backend, the backend development (Next.js API routes or Convex real-time backend) is included in the project scope. For mobile apps connecting to an existing backend, the scope is the mobile app and the API integration.
Yes — feature additions to existing React Native applications are a common engagement type. The code review at the start of the engagement identifies any technical issues that need addressing before new feature development.
Apple's App Store review takes 24–48 hours for most submissions. Rejections typically require 1–5 days to resolve depending on the issue. The project timeline accounts for one review cycle; significant Apple policy changes or unusual review outcomes are outside the project's control but are managed as quickly as possible.
Mobile app with Expo + React Native, both stores, from $45k. Apps that include a new backend (rather than connecting to an existing one) from $55k. Fixed-price.
Expo's managed workflow covers the majority of native device features. Platform-specific requirements (iOS widgets, Android background services) can be implemented with Expo bare workflow or custom native modules if needed — the scope definition stage identifies these requirements and prices them accordingly.
Tell Ryel about your project.
Describe what you’re building and what outcome you need. You’ll have a written, fixed-price scope within the week.