React Native, Flutter, or native: which is better?

For 80 percent of business apps, React Native or Flutter is the right choice: one codebase, 30 to 40 percent cost savings compared to native dual development. Native only for platform-specific features such as complex camera pipelines or GPU-intensive games. We primarily use React Native with Expo.

Is cross-platform a compromise on performance?

Not for business apps, portals, and e-commerce. React Native renders real native components on mobile; users notice no difference. Instagram, Shopify, and Discord use the same technology. For games and GPU-intensive applications, we recommend Unity or Unreal Engine.

Can we build just mobile or just web?

Yes. The architecture is flexible. You can start with mobile and add web later, or the other way around. We structure the codebase so that extending is not a rewrite.

We already have an app. Can you take it over?

Depends. Existing React Native or Expo apps are usually straightforward to take over. For native iOS/Android apps, a rebuild in React Native is often more economical than maintaining two codebases. We audit the codebase over 2-3 days first.

How does store submission work?

We prepare screenshots, store copy, app icons, and privacy labels and handle submission at Apple and Google. Apple typically reviews in 24 to 48 hours, Google within hours. The typical one or two correction rounds are covered in the fixed fee.

App Development for iOS, Android, and Web

Native apps for iOS, Android, and web from one codebase. From a 12-week MVP to a production app.

Discuss your app concept

Present everywhere, developed once

An app for iOS and Android realistically costs between 25,000 and 80,000 euros for a solid MVP in 2026, with 8 to 12 weeks of development time. That's the honest entry point; enterprise apps with deep system integration reach six- to seven-figure budgets. By MVP we mean the smallest version of the app that solves a clear problem and runs on both platforms. No feature pile-up, no three-month research phase. An MVP is not a prototype or a demo: it ships to the App Store, gets real users, and delivers data for the next iteration. Typical MVP scope: authentication, two to three core screens, backend integration, push notifications. Native or cross-platform? For over 80 percent of business apps, React Native with Expo is the right choice: one codebase, one design language, 30 to 40 percent cost savings compared to native iOS/Android dual development. Instagram, Shopify, Discord, and Microsoft Office run React Native in production. We only recommend native when platform-specific features are required, such as complex camera pipelines, ARKit/ARCore, or performance-critical animations in games. Store submission is its own craft. Apple typically reviews within 24 to 48 hours, Google within a few hours to one day. The common rejection reasons have been the same for years: missing privacy policy links, incomplete metadata, dummy content in the release build, or features behind a login the reviewer does not have. We prepare screenshots, store copy, app icons, and privacy labels and handle submission, including the typical one or two correction rounds. We build with React Native 0.78 and Expo SDK 53, connected to a .NET 10 backend. The backend runs on Fragon Cloud in Nuremberg, GDPR-compliant under Art. 28 GDPR, with no third-country transfers.

One codebase, three platforms

Development, testing, and maintenance happen once. That saves 30 to 40 percent compared to native dual development.

Consistent experience

Your users get the same features on iPhone, Android, or browser. No platform lags behind.

Fast updates

Web updates are live immediately. Mobile updates roll out via EAS Update without store review, as long as only JS code is affected.

From MVP to Production App

Transparent, agile, and goal-oriented to success.

Concept & Design

What should the app do? We clarify features, prioritize by impact, and design UI following Apple HIG and Material Design. Mobile-first, but web-ready.

Development

One codebase, weekly builds via EAS Build. You test on real devices and in the browser. Progress is always visible.

Backend & Integration

.NET API, integration with existing systems, push notifications via Expo Notifications, auth via OAuth or your own identity provider.

Store Release and Operation

App Store, Play Store, web deployment. We handle screenshots, store copy, privacy labels, and review rounds. Operation and OTA updates optional.

Technical Standards

React Native 0.78 with Expo SDK 53

Native performance on iOS 15+ and Android 9+ (API 28)

Responsive web version from the same codebase

Access to camera, GPS, push, and biometrics

OTA updates via EAS Update

.NET 10 backend on Fragon Cloud Nuremberg

What You Get

Native apps for iOS and Android

Web app from the same codebase

Design following Apple HIG and Material Design

Backend in C# / .NET 10 with PostgreSQL

Store submission and web deployment

Typical Scenarios

Users on All Devices

Some customers want an app, others prefer the browser. With cross-platform, you serve both without double effort.

Field Team

App for the road, web dashboard for the office. Same data, same logic, different interfaces.

Startup with Limited Budget

Instead of three teams for iOS, Android, and web: one that covers everything. Faster to market, lower cost.

Typical projects

Four recurring app projects. Not exhaustive, just a sense of the range.

MVP for an internal workforce app

Problem: An industrial company has field-service staff who today capture jobs on paper and re-key them in the office in the evening.

Solution: Eight to ten weeks of MVP with login, job list, photo upload, offline sync, and backend integration into the existing ERP, rolled out on 30 devices.

Cross-platform companion app

Problem: A web product has active mobile users, but the app-store presence is missing entirely.

Solution: Ten to twelve weeks of companion app on React Native with push notifications, shared auth flow with the web platform, and full store submission for iOS and Android.

White-label app for multiple tenants

Problem: A SaaS vendor sells its platform to customers who each want a branded app in their own store presence.

Solution: Twelve to sixteen weeks of codebase with a theme layer, a build pipeline for tenant builds, and automated store submission per theme.

Field-service app with offline sync

Problem: Technicians at a maintenance provider often work in areas without mobile coverage and need the app to work without connectivity.

Solution: Eight to twelve weeks of field app with local SQLite, conflict resolution on sync, photo annotations, and a job workflow including signature.

What does an app cost?

Under 15,000 euros, no serious MVP can be built. We'd rather say that up front than have both sides waste time. A typical business MVP lands between 20,000 and 40,000 euros; above that, you enter territory where an app needs more roles, deeper integration, or offline capability.

Guideline prices for Austria and Germany 2026. Actual cost depends on feature scope, backend complexity, and store strategy.
Scope	Price range	Duration	Typical use
MVP	15,000-40,000 €	8-12 weeks	Core feature, iOS and Android from one codebase, auth, backend integration
Mid-size	40,000-100,000 €	3-5 months	Multiple features, backend, auth, payment, push, and web version
Enterprise	100,000 €+	6 months+	Complex app, multiple roles, deep system integration, offline-first

Frequently Asked Questions

15,000 euros downward is a hard limit. A solid MVP with iOS and Android from one codebase typically lands between 20,000 and 40,000 euros with 8 to 12 weeks of development. That includes auth, two to three core screens, backend integration, push notifications, and store submission.