One codebase is usually the right call — but not always. The questions that decide it for us.
Most of the apps we build use one cross-platform codebase. It halves the work of shipping to iOS and Android and keeps both apps in step. But some products need native code.
When cross-platform wins
- Content, commerce, booking and dashboard apps
- Teams that want one set of engineers to maintain it
- Products that need to ship to both stores at once
When we go native
Heavy camera or audio work, complex background tasks, or deep platform features like widgets and watch apps can push us towards native — or a cross-platform app with native modules for those parts.
Either way, we decide in the first two weeks with a small technical spike, not by habit.