Native, Cross-Platform or PWA in 2026: How to Choose for Your First App

Every first app starts with the same question: native, cross-platform or a web app? In 2026 our answer for most founders is short. If you need iPhone and Android, build one app in React Native or Flutter. If iPhone comes first, or the app depends on Apple features such as widgets, a custom keyboard, audio or offline mode, build it natively in Swift. If people can use the product in a browser and you don’t need in-app purchases, start with a progressive web app (PWA) and add store apps later.

What changed since this guide was first written

Four things moved in 2025 and 2026, and each one affects the choice.

1. React Native now runs only on its New Architecture. The React Native blog calls version 0.82, from October 2025, “the first React Native that runs entirely on the New Architecture”. Version 0.88 followed in October 2026.
2. PWAs got easier on iPhone. With Safari 26 in September 2025, every website added to the Home Screen on iOS 26 and iPadOS 26 opens as a web app by default.
3. Both stores raised the bar for updates. Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later and an iOS 26 SDK, according to Apple’s requirements page. From 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36), with an extension to 1 November 2026 on request.
4. Store fees come off every sale. Apple charges 15% under its Small Business Program, and 10% on subscriptions after their first year. Google Play charges auto-renewing subscriptions under the first $1 million a year 10% plus a 5% billing fee in Australia, the EEA, Japan, the UK and the US, and 15% elsewhere.

Because of point 3, every app needs updates after launch. Whatever you pick, budget for at least one update a year to keep up with the stores.

Which approach fits your app

Your situation	Pick	Why
You need iPhone and Android from day one	One app in React Native or Flutter	One codebase, one team, both stores
The app sits on top of a web product you already run	React Native	It can use the same API, and a team that knows React can read the code
You are replacing an old app	Flutter	A clean rebuild in one codebase for both stores
iPhone comes first, or you need widgets, a keyboard, audio or offline mode	Native Swift	Full access to Apple features
People can use it in a browser, with no in-app purchases	PWA	No store review, and it installs from the browser

Two native apps, Swift for iPhone and Kotlin for Android, mean two codebases and twice the work on every feature. For a first version, that rarely pays off.

React Native or Flutter?

Both give you one app for both stores from one codebase. Of our published case studies, 9 use React Native and 7 use Flutter; our mobile app development page lists them. The choice usually comes down to what you already have:

• React Native fits when the app sits on top of a web product you already run. Traza had a CTO, web developers, a documented API and finished designs, but no mobile developers. We built the artist app in React Native on their own API and Figma designs, on a budget under $20k. It went live on both stores in early 2026.
• Flutter fits when you replace an old app. HealthyNikah ran on old Ionic and Angular code. We rebuilt it as one Flutter app and relaunched it on both stores in June 2026, with 3,200+ members moved over with their profiles and credits.

For an iPhone-first product, our iOS app development page covers native Swift; 20 of our case studies are native iOS apps.

Lessons from store review and payments

• Send the app to review early. Apple review can take one to two weeks. Traza went to review early instead of polishing until the last day, and was approved on both stores.
• Plan for a rejection. Apple first rejected HealthyNikah as one more dating app in a crowded category. We removed the dating language, appealed and got it approved.
• Use one tool for in-app purchases. HealthyNikah’s old custom billing kept failing and charged some members twice. It now runs on RevenueCat with Apple and Google in-app purchases, and Stripe for payments outside the stores.
• Put the store accounts in your name. If your Apple developer account is still waiting for approval, we can launch on ours.

What a first app costs

A first version typically costs $5,000 to $15,000 with us and takes 2 to 4 weeks, plus store review. Larger apps take longer: LEV took 4 months from the start to its market launch. The price depends on the number of screens, features such as payments, maps or video, and the admin panel you need.

For a market view: across 95 agencies, the median published MVP starting price is $13,234, and the middle half of starting prices runs from $6,617 to $20,000 (Rocketech MVP Price Index 2026, H2 edition). The $20,000 to $50,000 that the old version of this post quoted for a basic app now sits in the top quarter of the starting prices agencies publish.

How we would estimate it

1. Our project estimate turns your brief into user stories. You confirm what is in scope, and every hour in the budget traces back to a story you kept.
2. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour.
3. The unit economics show how many customers pay for the build and in which month it is paid back. You can change any starting number and the math updates.

Here is an example run of our estimate’s math with sample inputs, for an iPhone and Android dating app with matching, chat and a subscription. Every input is an assumption; only the arithmetic is ours. The build came to $6,600 to $13,600 and 5 weeks. With a $15 monthly subscription, a 70% margin after store fees, subscribers paying for 4 months, $20 to win each one and 300 new subscribers a month, 421 subscribers pay for the build and it is paid back in month 5. But lifetime value is only 2.2 times the cost to win a subscriber, below the 3× that counts as healthy. That run says: test the cost to win a subscriber before you spend on ads.

You can estimate your app’s cost and timeline in about four minutes. It is a planning range, not a fixed quote.

What we would do

1. Decide whether you need both stores on day one or iPhone first.
2. List the phone features the app needs: camera, maps, offline mode, widgets. They decide native or cross-platform.
3. If money moves in the app, decide early between in-app purchases and payments outside the stores.
4. Design for store review from the first screen, and send the app to review early.
5. Open the Apple and Google developer accounts in your company’s name.
6. Budget one update a year for new store requirements.

FAQ

What is the best mobile app development approach in 2026?

For iPhone and Android, one app in React Native or Flutter. For an iPhone-first app that needs Apple features such as widgets, a keyboard, audio or offline mode, native Swift. For a product people can use in a browser, start with a PWA.

Is it better to build a native or cross-platform app?

Cross-platform is usually better for a first version that needs both stores: one codebase and one team. Native Swift wins when iPhone comes first or the app leans on Apple features.

Can a PWA replace a mobile app in 2026?

For some products, yes. Since iOS 26, every website added to the Home Screen opens as a web app by default. You still need a store app for in-app purchases and a store listing.

React Native or Flutter: which should I pick?

React Native if the app sits on top of a web product you already run, as Traza’s did. Flutter if you are replacing an old app, as HealthyNikah did. Both give you one app for both stores.

How much does it cost to develop a mobile app in 2026?

A first version typically costs $5,000 to $15,000 with us and takes 2 to 4 weeks, plus store review. Across 95 agencies, the median published MVP starting price is $13,234.