Paris-based fleet SaaS (under NDA)
Re-architecting a fleet management ecosystem in Flutter
One Flutter codebase for drivers and managers, with native Kotlin & Swift modules where the hardware demands it.
Outcomes
- 01One shared Flutter codebase for Android and iOS
- 02Native Kotlin & Swift modules for background location and device features
- 03A modular architecture new developers can onboard into quickly
- 04Release pipeline that ships both stores from a single branch
The challenge
A growing fleet-management platform needed its mobile apps to keep pace with the product: drivers in the field, managers in the office, and a backend handling live vehicle data. Feature work was slowed by duplicated logic and platform-specific edge cases.
The approach
- Audit first. Mapped every screen, API call and native dependency to decide what moves to Flutter and what must stay native.
- Flutter core, native edges. Shared business logic and UI in Flutter; background location, sensors and OS integrations in dedicated Kotlin and Swift modules behind platform channels.
- Modular architecture. Feature modules with clear boundaries, so teams can work in parallel without stepping on each other.
- Incremental rollout. Modules shipped behind flags while the existing app kept serving users.
The goal was never "rewrite in Flutter". It was: ship features once, and make the native parts boring.
The result
The platform now runs on a single, well-structured Flutter codebase with a thin native layer — easier to extend, faster to release, and documented well enough for the wider team to own.
Replace this text with your own details and, where you can, real figures (release frequency, crash-free rate, time saved).
Next step
Got a system that's holding you back?
Book a free 30-minute call. You'll leave with a clear opinion on what to migrate, what to automate, and what to leave alone.