Three ways to put your system on a phone
- Native iOS in SwiftUIThe best experience on iPhone, including the latest system design language. Tokens in the Keychain, local cache for instant loads, a question box on every screen.
- Android (and cross-platform) in FlutterOne codebase for Android, with optional iOS. Biometric lock, encrypted cache, screenshots blocked and cloud backup disabled where the data is sensitive.
- Installable web app (PWA)Add-to-home-screen with Web Push notifications and no app store review. The right answer for volunteer and part-time users who will never install an app.
We have shipped all three. A racing operations client treats the native app as the main product, with executives checking per-horse profitability and occupancy from their phone. A large stable's riders and strappers get their day's rides and behaviour alerts through a Flutter app distributed by TestFlight and APK. A school rowing program's coaches receive tomorrow's session plan at six every evening through a progressive web app.
Server-driven screens
App store releases are slow and users do not update. Where it makes sense we build the app so that its screens, metrics and labels are described by the server. A new report or a new tab ships from the backend the same afternoon, with no app release. The native shell handles navigation, caching, authentication and the parts that need to feel truly native.
Security on a device you do not control
Business apps end up on personal phones. Ours assume that: short-lived web sessions and revocable 30-day device tokens, a token version that is bumped on password reset, biometric unlock, encrypted on-device caches, roles enforced in the API so that a staff account never receives financial fields even if the app asks for them, and privacy rules such as showing ownership shares without owner names.
Delivery and distribution
Internal apps do not always need a public store listing. We distribute through TestFlight, signed APKs on a private release repository, or a managed install link, and handle the certificates, signing and versioning. When a public listing is the goal we prepare the store assets, privacy declarations and review notes. Backend and app are built together, so the API contract is never a surprise to either side.