One codebase producing genuinely native iOS and Android applications, with the option to drop into platform code for the parts that need it.
What we reach for first
Apps whose value is in the workflow rather than the hardware: forms, lists, search, a queue of work synchronised with a backend. One team, one release cadence, and the saved effort spent on the server side where it usually belongs.
Not for anything living in the camera pipeline, an intensive graphics loop, or the deeper background execution APIs. When we hit that line we say so and go native rather than fighting a bridge.
The hard part is almost never the interface — it is what happens when the network goes away mid-task. We build the offline behaviour first, on the assumption that the connection will drop and the operating system will terminate the app, because in the field it does.
Where this appears on the site
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.
