apple
iOS native
Swift 6, SwiftUI, UIKit bridging, Core Data, StoreKit 2, HealthKit, ARKit, Live Activities, WidgetKit, App Intents.
- · Minimum: iOS 16
- · Xcode 16, Swift Concurrency
- · TestFlight → App Store
§§ · mobile app development
Mobile app developers shipping apps users come back to.
iOS, Android, React Native, and Flutter engineering for funded founders and enterprise teams. We ship to the App Store and Google Play on a clear 14-week cadence — and design for retention from week one.
Mobile app developers design and engineer applications that run natively on iOS and Android devices, or cross-platform through frameworks like React Native and Flutter. Not just the UI. The full surface — authentication, offline caching, push notifications, in-app purchases, deep links, background sync, analytics, and the CI/CD pipeline that ships it to the App Store and Google Play every two weeks.
The reason the work is harder than web is that mobile platforms are moving targets. Apple ships a new iOS every September, deprecates APIs, changes App Store review rules, tightens privacy manifests. Google does the same on a different cadence with Android. A mobile app developer's job is to keep the app shipping through all of it — not just to write Swift or Kotlin.
In practice, six work categories fill the hours for us: mobile-first UI and UX design, native or cross-platform engineering, backend APIs (often on our SaaS stack), release engineering, retention instrumentation, and the post-launch optimization loop where the real product work begins.
tl;dr
- Mobile app developers ship iOS (Swift), Android (Kotlin), or cross-platform via React Native and Flutter, end-to-end.
- Native: day-zero new-API access and 60fps edge cases. React Native: 14-20 weeks vs 28-36, single team, OTA updates via EAS.
- Eight-layer stack: backend, offline data, state, auth, in-app billing (StoreKit 2, Play Billing, RevenueCat), push, analytics, CI/CD.
- Five retention levers ship into every build: onboarding TTV, activation event, notification cadence, habit loops, cohort reporting.
- Pricing: $40K-$75K MVP (14 weeks), $75K-$200K production build (both platforms + retention), $150K+ enterprise with SOC 2 or HIPAA.
When to hire mobile app developers.
Six signals push a build native: offline-first behaviour, deep device-hardware access (camera, BLE, NFC, HealthKit), push notifications as your retention engine, App Store as a discovery channel, in-app purchases via StoreKit on the App Store or Play Billing on Android, and sustained session length. Three or more, build native or RN; fewer, ship a PWA.
- 01
Your product needs offline-first behavior
Fitness trackers, field-service tools, travel apps, logistics, note-taking. Web can approximate this with service workers; native does it cleanly with Core Data, Room, or SQLite and built-in background sync.
- 02
You need device hardware access
Camera (not file upload, real camera), microphone with low-latency capture, accelerometer, GPS with background tracking, BLE peripherals, NFC, biometric auth, HealthKit, Google Fit.
- 03
Push notifications are your retention engine
Web push is dying. Apple restricts it, Safari on iOS cripples it, notification permissions collapse every year. If your retention strategy runs on notifications, a native app buys you a 30–50 percentage point edge on deliverability.
- 04
Your users expect the App Store as a discovery channel
Consumer-first categories: fitness, meditation, finance, productivity, dating, utilities. Users search the App Store before Google. No app presence equals no shot.
- 05
In-app purchases or subscriptions are central
Apple IAP via StoreKit 2, Google Play Billing, RevenueCat for cross-platform reconciliation. Subscription products (fitness, creator tools, dating) live and die by native billing UX.
- 06
Session length is your primary engagement metric
Social, streaming, reading, gaming. 20-minute sessions on a mobile browser fight battery drain, tab switches, and notifications from other apps. Native wins every benchmark on sustained engagement.
§ 03 · the platforms
Four platforms. Senior on each.
Four platforms, senior on each: iOS (Swift + SwiftUI), Android (Kotlin + Jetpack Compose), React Native, and Flutter. Cross-platform builds use Expo for managed workflow and EAS Build. No juniors swapped onto your build.
google
Android native
Kotlin, Jetpack Compose, Room, Hilt, WorkManager, CameraX, Play Billing, Material 3, Adaptive Layouts.
- · Minimum: API 26 (Android 8)
- · Android Studio Meerkat, KMP-ready
- · Internal → Closed → Open → Production
cross-platform
React Native
RN 0.77+ with New Architecture, Expo EAS, Reanimated 3, MMKV, React Query, Zustand, React Navigation 7.
- · TypeScript strict mode
- · Over-the-air updates via EAS
- · Native modules in Swift/Kotlin
cross-platform
Flutter
Flutter 3.x, Dart 3, Riverpod, go_router, drift, Firebase, Impeller renderer, Material and Cupertino.
- · Strict null safety
- · Shorebird for code push
- · Native platform channels
Native vs. React Native.
React Native ships both platforms in 14-20 weeks with one team; native builds run 28-36 weeks across two teams but unlock day-zero new-API access and the highest performance ceiling. The call comes out of the Discover week. Pick wrong and you either burn $80K on a rebuild or ship an app that feels off.
| Factor | Native (Swift + Kotlin) | React Native |
|---|---|---|
| Build cost (both platforms) | 1.6–2.0× | 1.0× baseline |
| Performance ceiling | Highest (60fps at edge cases) | Excellent for 95% of apps |
| Time to ship both platforms | 28–36 weeks | 14–20 weeks |
| Native APIs at launch (iOS/Android) | Day-zero | 1–3 months lag |
| Team size (for parity) | 2 teams (iOS + Android) | 1 team |
| OTA updates | Store review each time | EAS Update (JS changes) |
| Complex camera / AR / ML | Best | Possible via native modules |
| Right call when | Apple-grade UX, heavy hardware, sub-1% performance edge matters | Content apps, SaaS companions, consumer MVPs, time-to-market |
We build both. The call comes out of the Discover week — not from a sales deck.
§ 05 · the full stack
The app, end to end.
Eight layers, one team: backend APIs, offline-first local data (Core Data, Room, SQLite), state management, authentication (Apple Sign In, passkeys, biometric guard), in-app billing (StoreKit 2, Play Billing, RevenueCat), push and messaging (APNs, FCM, OneSignal), analytics (Amplitude, PostHog, Firebase), release engineering with Fastlane, GitHub Actions, and EAS Build.
backend
API + server
Node.js, FastAPI, Supabase, Firebase, tRPC. GraphQL or REST depending on call patterns.
data
Local + offline
Core Data, Room, SQLite via drift, MMKV, WatermelonDB. Offline-first architecture by default.
state
State management
SwiftUI Observation, Compose State, Zustand, Riverpod, React Query. Minimal reactivity, maximum clarity.
auth
Authentication
Apple Sign In, Google Sign In, passkeys, magic links, biometric guard. Clerk, Auth0, or custom per project.
payments
In-app billing
StoreKit 2, Play Billing, RevenueCat, Stripe (non-IAP flows). Subscription receipts and webhook reconciliation.
retention
Push + messaging
APNs, FCM, OneSignal, Braze, Customer.io. Silent push, rich media, scheduled local notifications.
analytics
Instrumentation
Amplitude, Mixpanel, PostHog, Firebase Analytics. Sentry or Crashlytics for stability.
release
CI / CD
Fastlane, GitHub Actions, Bitrise, EAS Build. Automated testing, code-signing, screenshots, store deploy.
§ 06 · the unfair advantage
We don't just ship apps. We engineer retention.
Five retention levers ship into every build: onboarding time-to-value under 60 seconds, one named activation event predicting Day-30 retention, notification cadence tuned per cohort, habit loops (streaks, daily rituals, progressive unlocks), and weekly cohort reporting. Most agencies stop at launch. Day-7 retention is 12% and install-to-active collapses. That's a missing discipline.
lever · 01
Onboarding time-to-value
First moment of utility < 60 seconds from install. Cut every screen between open and win.
lever · 02
Activation event
One named event that predicts Day-30 retention. Instrument it. Optimize the funnel to it.
lever · 03
Notification cadence
Right moment, right channel, right frequency. Over-push and users disable. Under-push and they forget.
lever · 04
Habit loops
Streaks, daily rituals, progressive unlocks, social proof. The difference between a tool and a habit.
lever · 05
Cohort reporting
Weekly cohort review. Retention curves by acquisition source. Winners scale, losers get cut.
benchmark
22% → 38%
Day-7 retention lift
A typical Day-7 retention audit, shipped over 90 days. We find the activation event, fix the onboarding funnel, tune the notification cadence, add a habit loop, and wire cohort reporting. You keep the work. Your team runs the loop from week 13.
Start a retention audit§ 07 · the process
From brief to App Store in 14 weeks.
Longer than web because mobile carries App Store review, TestFlight, and phased rollout overhead. Shorter than industry average because we start building in week 3. Discover (1 wk), Design (2 wk), Build (6 wk), Internal + External TestFlight (2 wk), submission and phased rollout (3 wk).
- week 1 · discover
Brief, personas, activation event
Goals, constraints, user research synthesis, platform decision (native vs RN), tech spike if required. Activation event and Day-7 target set here.
- week 2–3 · design
Flows, visual system, high-fi screens
User flows, wireframes, Figma design system, 15–25 high-fidelity screens, prototype for usability testing, App Store preview comps.
- week 4–9 · build
Engineering, APIs, payments, instrumentation
Weekly demos. Backend + mobile in lockstep. Analytics events wired as features ship, not at the end. Crash reporting and observability from day one.
- week 10 · internal
Internal TestFlight + Play Internal Testing
Our team and yours on both platforms. Dogfooding. Bug triage. Performance profiling on real devices (iPhone 11 through 17 Pro, Pixel 6 through 10).
- week 11 · external
External TestFlight + Closed Beta
Up to 10,000 testers on iOS, staged rollout on Android. Feedback collection, session recording, analytics review, last-mile polish.
- week 12 · store
App Store + Google Play submission
App Store Connect setup, Play Console setup, screenshots, previews, privacy manifests, data-safety form, App Tracking Transparency copy. Review turnarounds typically 24–72 hours for first pass.
- week 13 · launch
Phased rollout + launch-day monitoring
1% → 5% → 20% → 50% → 100% over 5 days. Crash rate, ANR rate, session duration, and activation funnel watched in real time. Rollback plan staged.
- week 14+ · optimize
Retention loops + monthly reviews
Day-7 cohort analysis, activation funnel tuning, notification experiments, habit-loop A/B tests, App Store keyword optimization, ratings and reviews management.
Three engagement tiers.
Three engagement tiers: $40K-$75K MVP (14 weeks, single platform or RN), $75K-$200K production build (both platforms, retention instrumentation, launch playbook), $150K+ enterprise (SOC 2 posture, SSO, HIPAA when needed, MDM, offline-first architecture). Published ranges, senior delivery, clear scope. If the scope balloons, we tell you before the invoice does.
mvp
Mobile MVP
$40K–$75K
14 weeks. Single platform (iOS, Android, or RN cross-platform). Core flows, auth, payments, push, analytics, CI/CD. Ready for real users.
Start an MVPmost picked
production
Production build
$75K–$200K
Both platforms. Native or RN. Deep integrations, custom backend, full design system, retention instrumentation, launch playbook.
Start a production buildenterprise
Enterprise engagement
$150K+
Multi-app ecosystem. SOC 2 posture, SSO, advanced security, HIPAA if needed, MDM, offline-first architecture, multi-region deployment.
Scope an engagementverified · certified · proven
Upwork Top Rated+
Trustpilot 4.9 ★ · 70 reviews
DUNS 650878346
UN Global Tier 1Mobile app developer FAQ.
Direct answers on what mobile app developers do, app build costs, timelines, the native-vs-RN call, App Store and Play submission, retention audits, and design coverage. Canonical references at developer.apple.com and developer.android.com.
What do mobile app developers do?
Mobile app developers design and engineer applications that run natively on iOS and Android devices, or cross-platform via React Native and Flutter. That covers product discovery, UI/UX, native or RN code, backend APIs, push notifications, payments, analytics, CI/CD, store submissions, and post-launch retention.
How much does a mobile app cost to build?
MVP runs $40K–$75K on a 14-week timeline. Production-grade with both platforms and retention instrumentation lands $75K–$200K. Enterprise with SOC 2, SSO, or HIPAA exceeds $150K. Prices are scope-bound and published in the SOW before contract sign.
How long does it take to build a mobile app?
14 weeks from brief to App Store launch for an MVP. Discover (1 wk), Design (2 wk), Build (6 wk), Internal TestFlight (1 wk), External TestFlight (1 wk), App Store review (up to 1 wk), Launch + 1 week Optimize. Production apps run 20–28 weeks.
Should I build native or React Native?
React Native for content-heavy apps, standard UI patterns, and React-fluent teams. Native (Swift + Kotlin) for day-zero access to new platform features (HealthKit, ARKit, Live Activities, Android Auto), deep hardware integration, or first-party-feeling UX. We recommend the call on the Discover week.
Do you handle App Store and Google Play submission?
Yes. App Store Connect setup, Google Play Console setup, screenshots and previews, privacy manifests, data-safety declarations, App Tracking Transparency copy, phased rollout plan, review responses. Most of our MVPs pass App Store Review on the first submission.
Can you help improve retention on an existing app?
Yes. Day-7 retention audit: funnel instrumentation, notification cadence, onboarding time-to-value, activation metric identification, cohort analysis. Typical output is a 90-day plan targeting a named retention lift (e.g., Day-7 from 22% to 38%) with engineering and experiment budget attached.
Do you provide mobile app design as well as development?
Yes. Mobile-specific UI/UX is core — see our dedicated UI/UX design service. User research, information architecture, flows, visual system, high-fidelity Figma screens, prototypes, and a handoff-ready design system.
§ 10 · mobile development in 2026
What changed for mobile builds.
Three changes reset mobile build decisions in 2026: React Native crossed the 0.74 line and is now production-credible for commerce and content apps, Apple shipped iOS 17 minimum-deployment requirements for new submissions, and Android 15 plus Material 3 Expressive made the platform's design language a moving target again.
The cross-platform versus native call is now a real conversation. React Native's new architecture (Fabric and TurboModules) shipped, closing most of the historical performance gap with native, and Apple's UIKit and SwiftUI docs show what native-only still buys you: deep platform features, instant adoption of new OS APIs, and predictable App Store review timelines. The right answer depends on whether your differentiator is feature surface or platform-specific moments.
On the Android side, Android's Material 3 Expressive docs codify the new tokens, motion specs, and dynamic-colour rules; any app shipping in 2026 that does not opt into the new design language looks two years old at install. For commerce apps tied to Shopify or a headless storefront, React Native plus Shopify's mobile SDK remains the fastest path to feature parity across both stores.
What this means for your project: in 2026, default to React Native for commerce, content, and most B2C apps; pick native (Swift, Kotlin) only when the differentiator is platform-specific (ARKit, CameraX, Live Activities, on-device ML). Budget for a six-month post-launch retention sprint; the App Store install is not the win.
Related reading + work: See our native versus hybrid mobile framework, the Shopify mobile app builders comparison, and our iOS development, Android development, and React Native development pages for adjacent work.
related · services
ready for the store
Brief us. Ship to the App Store in 14 weeks.
One business day. A senior mobile developer reviews the brief, writes the plan, sends it back. If we're not the right fit, we say so — and often point you to a better option.
Published · Last updated .