Mobile apps people actually keep on their phone

One codebase, both platforms. For the overwhelming majority of business apps the performance difference against native is small enough that users never notice it, while the saving on build and maintenance is substantial and permanent.

We default to React Native, because it shares skills and often code with a React web stack, which matters more over five years than any benchmark. Flutter is the better choice when the interface itself is the product — heavy animation, a pixel-identical design system across platforms.

Swift and Kotlin, built per platform. This costs more to build and roughly twice as much to maintain, so it needs a reason beyond preference.

Good reasons exist: graphics-intensive or 3D interfaces, heavy augmented reality or on-device computer vision, needing a platform API on the day it ships, or products where latency is the point — professional camera and audio tools. If you are in one of those, we will say so.

Native is not the default any more. A progressive web app is found through search, opens from a link, needs no install, avoids store commission and updates the moment you deploy.

It gives up some ground: deep hardware access, background work, and push on iOS remains weaker than on Android. A common good answer is both — a web app for reach, plus a thin native app for the people who use it daily.

Phones lose signal. An app that assumes connectivity fails in the exact places field teams work — basements, warehouses, rural sites, in transit. Offline-first means the app stays usable and reconciles when the connection returns.

That reconciliation is the hard part, not the caching: deciding what happens when two people changed the same record offline. We design that rule with you rather than letting the last write silently win.

Getting into the App Store and Play Store is a process with its own rules: review guidelines, privacy declarations, data-safety forms, age ratings, test builds for your team.

Then it keeps going. Apple and Google ship OS versions every year and periodically raise the minimum SDK, so an app left untouched will eventually stop being accepted. Mobile maintenance is not optional, and we say what it costs before you commit.