"Should we build native or cross-platform?" — that's still the first question in nearly every mobile app project we take on. The answer in 2026 is different from what it was in 2020, and getting it wrong can cost you 30 % of your project budget.
State of the art: three realistic choices
React Native
With Meta's New Architecture (Fabric + TurboModules) as the default since 2024, React Native has closed the gap to native in most areas. Performance is comparable for 95 % of use cases, and the ecosystem is enormous.
Where we use it: customer-facing apps with traditional UI (e-commerce, social apps, SaaS apps), teams that already know React/TypeScript, projects that need rapid iteration.
Flutter
Flutter has grown into a serious contender, especially for apps with custom design. The Dart language is still a barrier for some teams, but performance is excellent and hot reload remains best-in-class.
Where we use it: apps with intensive custom animation, projects requiring pixel-perfect design consistency across platforms, teams without a React background.
Native (Swift/Kotlin)
Native isn't dead. It's just become a sharpened tool for specific needs: AR/VR, complex background processing, integration with platform-specific APIs (HealthKit, CarPlay, Android Auto), or when 60+ fps in a complex UI is critical.
Where we use it: games, AR apps, HealthTech that needs HealthKit, FinTech with biometric requirements, and apps where "feels native" is a competitive advantage.
What has changed since 2020
- Cross-platform is no longer a compromise. For 90 % of commercial apps, the difference between RN/Flutter and native is imperceptible to end users.
- Apple and Google have tightened the rules. Missing privacy manifests, incomplete App Store Connect meta, or poor accessibility gets the app rejected before it reaches users.
- App Store approval takes longer. Plan for 24–72 hours for first approval. Build it into the launch timeline.
- "Mobile first" has been replaced by "mobile only" for many use cases. If your app doesn't work perfectly on a 5.5-inch screen, you've lost.
User experience: what separates the winners
Onboarding
The first 30 seconds decide whether the user keeps the app. Every additional mandatory step in onboarding costs you 7–10 % of users. Require minimum, offer maximum, and let users explore before you demand data.
Offline-first
Mobile users have poor network half the time. Apps that crash or show a white screen without internet lose users fast. Implement offline-first architecture from day one — cache aggressively, sync optimistically, handle errors gracefully.
Push notifications without being annoying
Push is the most powerful retention tool — and the easiest way to lose users. Request permission at the right moment (not at first open), send relevant content (not marketing spam), and respect the user's time zone.
Security and privacy
GDPR was just the warm-up. In 2026 we see stricter enforcement, both from data protection authorities and from Apple/Google themselves. Concretely:
- Never store sensitive data in AsyncStorage/UserDefaults without encryption
- Use Keychain (iOS) / Keystore (Android) for tokens and secrets
- Implement certificate pinning for finance and health apps
- Request the minimum permissions possible, and explain why you need them
- Maintain an up-to-date privacy policy, and show it on first open
What a mobile app actually costs
There's no honest "starting price", but here are typical ranges from our projects:
- MVP (one platform, cross-platform, 4–6 screens): 250 000 – 400 000 NOK
- Full commercial app (both platforms, 15–25 screens): 600 000 – 1 200 000 NOK
- Native app with complex integration (health, AR, finance): 1 500 000+ NOK
On top: 15–25 % annual maintenance to keep the app current against new OS versions, Apple/Google policy changes, and dependency updates.
Our recommendation
Start by defining the user's job-to-be-done, not the technology. Once you have that, the platform choice is often obvious:
- Need to be on App Store and Google Play with traditional UI? → React Native or Flutter.
- Need deep platform integration, AR, or max performance? → Native.
- Unsure? → Build a cross-platform MVP, validate, then decide if native is needed.
At Inovix we've built eight mobile apps over the past three years — in React Native, Flutter, and native. If you're considering building, we can give you an honest assessment in 20 minutes.
