Choosing a mobile framework, and building offline-first field apps and customer apps that hold up in daily use.
Native, Flutter, React Native, Kotlin Multiplatform or Ionic/Capacitor and PWAs: how they differ and which one to pick in which situation.
Where Flutter is the right choice for a business app, where it is not, and what to settle before the first sprint, as Flutter stands in 2026.
When a PWA or a Capacitor app is the right mobile choice, what iOS web apps can and cannot do in 2026, and where web tech stops being enough.
When Kotlin Multiplatform and Compose Multiplatform fit a mobile app in 2026, their stability on iOS today, and how to adopt KMP one module at a time.
When Odoo's own mobile app is enough for drivers and technicians, when to build a custom app on the JSON-2 API, and how to handle offline and API keys.
When separate Swift/SwiftUI and Kotlin/Jetpack Compose apps are worth two codebases, when they are more than you need, and how to keep them in step.
Local database, sync queue, conflict resolution and the real limits of background sync on iOS and Android, for teams building field apps.
Where React Native and Expo fit a business app in 2026, what the New Architecture changed, and where another framework is the better choice.
Developer accounts, review guidelines, TestFlight and Play testing tracks, privacy labels, staged rollouts and what over-the-air updates may change.
The decisions that make a mobile app take longer and cost more: platforms, offline, integrations, design, compliance, release and maintenance.
Every Odoo 19 app a growing business uses, in the order we would roll them out: setup, sales, operations, finance, HR, and the new AI features.
Read the series from part one →