Getting started with native and cross-platform mobile
This is one of those topics that looks small until it costs you something. A short on-ramp to native and cross-platform mobile for teams who have not touched it before.
Mobile releases are slower to correct than web ones, so the cost of shipping a mistake is higher. The version that survives contact with a real deadline is the simple one.
What is actually at stake
Cross-platform is a team decision as much as a technical one. Small and consistent beats large and occasional here. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.
Your first week
- Find out what is already in place
- Heavy device integration still favours native
- Change one thing and measure it
Shipping one codebase badly is worse than two well. The reasoning matters more than the rule, because the rule has exceptions. Assume whoever inherits this will have half your context and none of your patience.
What this looks like day to day
The version of the app your customers are running is rarely the one you just shipped. 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
- Shipping one codebase badly is worse than two well — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Most of the value here comes from doing the first two things, not all of them.