"Should we build native or not?" used to have a simple answer. In 2026 it doesn't, because the gap between the options has narrowed dramatically — cross-platform frameworks now deliver near-native performance, and progressive web apps handle the majority of everyday use cases. So the question becomes: which approach fits your product, audience and budget? We build mobile both ways (the Dentalk apps are fully native), so here's a straight comparison.
The three approaches
- Native. Built specifically for each platform — Swift/SwiftUI for iOS, Kotlin/Compose for Android. Best performance and deepest device access; two codebases to build and maintain.
- Cross-platform. One codebase via React Native or Flutter that compiles to real iOS and Android apps. Near-native performance with most of the cost saving of a single codebase.
- PWA (Progressive Web App). A website that behaves like an app — installs to the home screen, works offline, sends push notifications. One codebase, no app store required, and discoverable on Google.
Side by side
| Factor | Native | Cross-platform | PWA |
|---|---|---|---|
| Performance | Highest | Near-native | Good for most |
| Device access | Full | Most, via plugins | Limited |
| Build cost | Highest | Medium | Lowest |
| Codebases | Two | One | One |
| App store presence | Yes | Yes | Optional / wrapped |
| Discoverable on Google | No | No | Yes |
| Install friction | Store download | Store download | One tap, no store |
| Offline support | Yes | Yes | Yes (with caching) |
| Maintenance | Two to maintain | One | One, ships instantly |
What each costs
Cost tracks closely with how many codebases you maintain. As a rough guide: a PWA runs about 40-60% of the cost of building equivalent native apps for both platforms; a cross-platform build runs about 60-70% of dual-native. The maintenance difference compounds — a single codebase means every fix and feature ships once, not twice. For a tight budget or a fast launch, that gap is decisive.
When to choose each
Choose native when raw performance or deep hardware access is non-negotiable: real-time video, AR, advanced camera work, health-sensor integration, or a flagship app where every millisecond of polish matters.
Choose cross-platform when you want real app-store presence on both platforms, fast, with one core team — the smartest default for most business and consumer apps that don't push the hardware to its limits.
Choose a PWA when reach, speed to market and low cost matter most: content, catalogues, dashboards, internal tools, e-commerce and simple business apps. No install friction, indexable on Google, and updates ship instantly.
A five-point checklist before deciding: name your top three user journeys; list every device feature those journeys need; define offline behaviour per journey; set your release cadence; and confirm who'll maintain it. If you can't answer these in writing, you're not ready to pick a framework — the decision is guesswork until you can.
The 2026 reality
Two shifts changed the maths. First, cross-platform frameworks (React Native, Flutter) matured to near-native performance, making "native" accessible to startups without two teams. Second, the web platform gained push notifications, background sync, file access and more, while regulatory pressure pushed Apple to open iOS further — so PWAs are more capable than ever. The practical result: for a large majority of products, a PWA or cross-platform app is the right first move, and fully native is reserved for genuinely demanding apps. Match the technology to the product's core behaviour, not to whatever sounds most impressive.
How we chose native for Dentalk
A concrete example: Dentalk is a social app with live video streaming, real-time chat and one-to-one and group calls. That core behaviour — low-latency, real-time video with co-hosts, powered by Agora — is exactly the case where native earns its cost. So we built it native: Swift on iOS, Kotlin and Jetpack Compose on Android, over a shared backend. If Dentalk had been a content or catalogue app, we'd likely have recommended cross-platform or a PWA instead. The approach follows the product, every time.
Weighing a mobile build? See our mobile app development service, or tell us what you're building and we'll recommend the right approach — not the most expensive one.