The real cost of ignoring native and cross-platform mobile
It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Nobody bills you for neglecting native and cross-platform mobile. The cost shows up somewhere else.
The version of the app your customers are running is rarely the one you just shipped. Check it against what you would want a competitor's site to get wrong.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Cross-platform is a team decision as much as a technical one
- Rework, once the problem is finally visible
Heavy device integration still favours native. Small and consistent beats large and occasional here. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
Turning this into a decision
Shipping one codebase badly is worse than two well. The cost of getting this wrong is rarely visible on the day it happens. If two people in the business would answer this differently, that gap is the actual problem.
What this looks like day to day
You do not control the device, the network, or the operating system version, and the design has to accept that. Three things worth confirming about native and cross-platform mobile before you move on:
- Someone can say what the current setup is without going to look
- Cross-platform is a team decision as much as a technical one — and you know whether that is true here
- There is a way to tell whether the last change to this helped
None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.