Our take, no hedging: for most small businesses in Moldova a PWA covers about 80% of what a native app does, at a fraction of the cost. Go native only when you need games, heavy logic, exotic hardware or a UX that must be flawless every single time. The rest of this article is the why — built on real technical differences, not marketing.

What a PWA is, briefly

A PWA (Progressive Web App) is essentially a website that behaves like an app. You open it in a browser, and the phone offers to "install" it on the home screen — an icon appears, no address bar, just like any other app. It works partly offline (visited pages are cached), can send notifications and loads instantly on the second visit. Technically, a service worker and a manifest file do the magic. Nothing to download from a store.

And a native app?

A native app is code written specifically for iOS (Swift) and Android (Kotlin), or through a cross-platform framework. You download it from the App Store or Google Play, it fully installs on the phone and gets full system access. That's where the cost gap comes from: you're effectively building and maintaining two products, plus going through store approval.

Cost and time — the real gap

A PWA is built once, like a website, and costs about as much as a good site. A native app usually demands several times the budget and time: two platforms, developer accounts (Apple charges $99/year), store reviews that can drag on for days. For an SMB budget, that matters a lot.

Access to phone features

Native dominated here for years, but the gap has narrowed a lot. A modern PWA already reaches:

  • Camera and microphone — QR scanning, photos, video.
  • Geolocation — maps, delivery, "find the nearest point".
  • Payments — via the Payment Request API, including Google Pay; Apple Pay works in Safari with limits.

What stays hard or impossible on the web: reliable Bluetooth on iOS, NFC, advanced sensors, deep system integration. Got a medical Bluetooth device or a fitness band? You probably need native.

Push notifications and the iOS catch

On Android, PWA push has worked for a long time, no issues. On iOS it only arrived in version 16.4, and only if the user first adds the PWA to the home screen. Many don't. If notifications are the heart of your product, native is safer — on the web you lose a slice of your iPhone customers.

Stores, trust and updates

App Store presence adds credibility — some customers search there directly. A PWA, though, updates instantly: fix a price and everyone sees it at once, with no wait for Apple's approval and no download for users. It's indexable in Google, so it brings organic traffic too. And with no store, you pay no sales commission.

Our verdict

Catalog, services, bookings, a small shop — start with a PWA and validate real demand. A game, a social network, complex logic or special hardware — go native from the start. At shadowforge we tell you honestly which option solves your problem more cheaply, and we'll even plan the move from PWA to native when the numbers call for it — write to us for an app project assessment.