Capability
Mobile Development
React Native applications built and shipped to both stores from a single codebase, including the parts that are never in the tutorial: release process, device variation, and store review.
What is actually included
- Cross-platform applications for iOS and Android from one codebase
- Native module integration where the platform bridge is unavoidable
- Release, signing, and store submission handled as a repeatable process
- Offline behaviour and sync against a server that is sometimes wrong
Two stores, one codebase
I have led and built cross-platform native applications for iOS and Android in React Native. The appeal is obvious – one codebase, two platforms – and it is largely real, provided everyone is honest about the ten to twenty per cent that is not shared and never will be.
The parts that are never in the tutorial
Building the screens is the easy half. The half that consumes the schedule is everything around it: signing and provisioning, store review, staged rollout, crash reporting, supporting the device somebody in the field is still using, and deciding what the application does when the network is there but the server is wrong.
- Release, signing, and store submission as a repeatable process, not a ritual
- Native module integration where the bridge is unavoidable
- Offline behaviour and sync conflict handling decided deliberately
- Crash and error reporting wired up before launch rather than after the first incident
A mobile application is a distribution problem as much as an engineering one. The version your users are running is the one they last chose to update, which means old clients must keep working against a moving server for far longer than anyone plans for.