Native or cross-platform? The honest decision tree
Mobile · 4 min read
Native or cross-platform? The honest decision tree
Ask three agencies whether your app should be native or cross-platform and you’ll get three confident, contradictory answers — each one matching whatever that agency happens to build. So here’s the framework we actually use with clients, by budget, team, and roadmap. Not by fashion.
Start with the questions that decide it
Who is the app for? Internal tools — a scanning app for the warehouse, a field checklist for crews — almost never justify two native codebases. Consumer apps competing for attention in an app store sometimes do.
What hardware does it touch? Camera, GPS, and push notifications are solved everywhere. Bluetooth scanners, printers, and background services get platform-specific fast — the deeper the hardware integration, the stronger the case for native.
Who maintains it in year three? Two codebases cost roughly twice as much forever — every feature, every OS update, every bug, twice. If the budget conversation is tight now, it will be tighter in year three.
Does the last 5% of polish pay? Buttery platform-perfect animation matters for a consumer brand. It does not matter to a picker scanning pallets — that app is judged on speed, reliability, and battery life.
Our defaults, stated plainly
For most business apps — customer companions, field tools, portals in your pocket — one cross-platform codebase is the right call: one team, one release cycle, budget left over for the features users actually notice. We go native when the app is the product, when hardware integration runs deep, or when platform-specific performance is the difference between adopted and abandoned.
Be suspicious of anyone whose answer doesn’t depend on your answers. The framework matters more than the framework.
Either way, the process is the same: wireframe every screen before build, ship agile releases to real devices through TestFlight and Play beta tracks, and support the app as OSes and devices change. The technology choice is a means; the app your customers keep is the end.