When native and cross-platform mobile is worth the effort
This is one of those topics that looks small until it costs you something. Native and cross-platform mobile is not free, and pretending otherwise leads to bad decisions.
The version of the app your customers are running is rarely the one you just shipped. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.
When it is worth it
Cross-platform is a team decision as much as a technical one. Small and consistent beats large and occasional here. Doing this properly once is usually cheaper than doing it approximately three times.
When it is not
If nothing downstream depends on it and nobody is complaining, it can wait. Where this goes wrong is almost never a lack of knowledge.
How to decide
Shipping one codebase badly is worse than two well. The cost of getting this wrong is rarely visible on the day it happens. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
How to tell if yours is fine
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
- Heavy device integration still favours native — and you know whether that is true here
- There is a way to tell whether the last change to this helped
If any of that sounds like a description of your current setup, it is fixable.