Why you don't need a native app in 2026

This is a post my client would hate if he sold native apps. Lucky for me, he builds web applications.

Five years ago, native app was the answer to everything. Client wants App Store presence? Native app. Wants push notifications? Native app. Wants offline support? Native app.

Today, PWA does all that. And costs R$25k instead of R$80k.

I’m not against native apps. But I’m here to be honest. If your client doesn’t need GPS running 24/7 or access to specific hardware sensors, they don’t need a native app.

What’s a PWA (and why it’s won so much in 2026)

PWA stands for Progressive Web App. Basically it’s a website that behaves like an app. Installs on home screen, works offline, has push notifications.

Chrome, Safari, Edge, Firefox all support PWAs now. Android recognizes when you install a PWA and treats it like a normal app. It’s indistinguishable from native apps for most users.

The big problem PWA had was Safari. Steve Jobs wanted everything to be native, so PWA never worked properly on iOS.

That changed. iOS 17 and 18 have robust support now. Push notifications work. Offline works. What still doesn’t work? Home screen install on iOS is kind of awkward, but it’s a minor detail. It works.

When native app actually makes sense

Before you kill every native project: real cases exist.

If your app needs GPS running in the background all the time, transmitting coordinates, you need native. Only native has access to GPS with the screen off.

If you need integration with specific phone hardware (magnetometer, real-time accelerometer for something custom), native has the advantage.

Video calls with bad quality? PWA can do it, but latency is always worse. Native has libraries that optimize for this.

I built a project for a fitness app. It needed to track user movements in real-time with the camera. We tried PWA. It was slow. Camera latency was bad for real-time pose tracking.

Then we built native. Worked well. But cost R$120k. Was it necessary? For that specific case, yes. But it’s the exception.

The math of cost

Let me be very practical here.

Well-built PWA with push notifications, offline, sync, installable: R$25k to R$35k. You build once. Same codebase for all platforms.

Native iOS app: R$40k to R$60k. Native Android app: R$40k to R$60k.

Want to support both? R$80k to R$120k. Now you have two codebases. Two different bugs. Two deployments.

Your client wants a small UI change? That’s R$5k of adjustments on the native app. On PWA? R$500.

The math is brutal. PWA wins in most scenarios.

What PWA delivers today

Push notifications work real-time. You send a notification via service worker, user gets it immediately. Even if the tab is closed. On iOS too now.

Offline works. You cache data and use IndexedDB. The app runs normally even without internet. When connection returns, it syncs.

Install prompt is that popup asking to add to home screen. On Android, it’s native. iOS is more limited, but you can give users instructions.

Background sync. You submit a form and want to guarantee it goes even if the user closes the app? Background sync retries later.

For a dental clinic doing scheduling? PWA solves everything. Offline? Patient schedules without internet. Push notification? Confirms appointment an hour before. Installable? Lives on the phone home screen.

What PWA still doesn’t do

Doesn’t access all sensors. Want real-time gyroscope access? Native app. Want phone contacts? Native app on iOS still doesn’t allow it. Want Apple Wallet or Google Pay integration? That’s complicated.

Background GPS is weak. PWA can use Geolocation API but doesn’t run in background with screen off. That’s native only.

Large file downloads are more transparent on native. On PWA you can do it, but it’s more manual.

Performance on native is always slightly better. That’s true. But for 90% of apps, the difference is imperceptible. Your user won’t feel the difference between 15ms and 50ms.

The client who “needs an app”

I have these conversations every week.

Client: “I want a native app, I need to be on the App Store.”

Me: “Why?”

Client: “Because my competitors have apps.”

That’s not a reason. Being on the App Store doesn’t mean more users. A bad app on the App Store is worse than a good PWA off it.

I proposed PWA to a logistics client. They thought it was strange. I built a PWA with install prompt, push notifications, offline. Six months later, 80% of users were accessing the installed PWA on home screen.

Nobody asked to be on the App Store. Nobody said “why isn’t this on the app store”. They just used it normally.

Real comparison: iOS vs Android vs PWA

The question every client asks is “which platform do I target?” The answer changes completely with PWA.

Native iOS app: R$40k-60k USD equivalent, 4-6 weeks of development, need Mac to compile, device testing is manual. Updates release once per week through Apple, can be rejected without clear reason.

Native Android app: R$40k-60k USD equivalent, 4-6 weeks, testable with decent emulator, updates on your schedule (direct to Play Store).

Both (iOS + Android): R$100k+, two teams, two codebases, bugs appear differently on each platform. You become a project manager instead of a dev.

Well-built PWA: R$20k-35k USD equivalent, works on all browsers from day one, single codebase, updates when you deploy, zero App Store or Play Store dependency.

Here’s the cruel detail: the client who paid R$100k for native will want maintenance. That tiny tweak taking 30 minutes on PWA takes 3 hours on native because you need to compile, test on device, make a release, wait for approval.

Why App Store seems important but really isn’t

There’s psychology at play. Client sees their app on the App Store and thinks “I’m important now”. It’s real. But it’s an illusion in business terms.

A dental clinic doesn’t need the App Store to gain patients. It needs to be findable on Google and have a fast site that converts. PWA does that better.

E-commerce? Needs to be discovered, be fast, easy to buy. PWA excels at all of it.

App Store mattered in 2015 because it was the only place to find apps. In 2026? You can discover almost anything through browser or search. App Store got smaller.

The smart path

If you’re between native and PWA, choose this way:

First: build PWA. Invest R$20k-30k, have product in hand in 6 weeks. Use it with real customers.

After 6 months with PWA: if you really need native (real usage metrics, concrete performance feedback), then build it. But you’re seeing actual demand.

Most of the time? PWA is enough and you saved R$50k and 10 weeks.

Quick decision table

Situation	Choose
Clinic site, few users	PWA
E-commerce under 10k visits/month	PWA
Productivity app with offline sync	PWA
GPS tracker 24/7 while running	Native
Real-time sensor (accelerometer)	Native
Video calls as main feature	Depends (PWA if tolerable, Native if critical)
Apple Wallet/Google Pay integration	Both (PWA + Native)

The future

PWA will get better. Google is investing heavily. Apple was kind of forced into it. We expect new APIs like Web Monetization and Payment Request to close the gap even more.

Native won’t disappear. It’ll always exist. But for most projects? PWA is the sensible choice.

Choosing native for status or because it feels more professional is wasteful. It’s throwing your client’s money away.

Checklist before deciding on native

• Really need GPS running in background?
• Need access to specific hardware (real-time camera, sensors)?
• Video calling is core business and performance is critical?
• Have real budget to maintain two codebases?
• Need to be on the App Store or is it just vanity?
• Already tested PWA with the client?
• Calculated total cost over 3 years including maintenance?

Read also: PWA without app store | How much does a custom web system cost | Scope is the most important dev skill

Build a PWA. Your client will be happy with the cost and you’ll sleep better.