Case study · Our own product
Four documents, four expiry dates, four different institutions. One app that remembers all of them.
Motorix is our own product, built on exactly the stack we would build a client's on: Kotlin Multiplatform, one codebase, two native apps released together. It is the proof that the approach survives contact with a real store listing and real users.
The problem
A car in Romania needs four separate documents, each renewed at a different interval, each issued by a different body, none of which reminds you. Miss one and the fine arrives before the reminder does.
The app
No dashboards to configure, no reports to run. The garage screen leads with whatever expires next.
What is inside
RCA, ITP, CASCO, rovinietă, service receipts, fuel receipts and the vehicle registration. Text recognition runs on the device — ML Kit on Android, the Vision framework on iOS — and Gemini turns the raw text into structured fields. Photograph the policy, the expiry date fills itself in.
A document ninety days out is green. Thirty days out it turns amber, then orange, then red, then expired — the colour is the whole message, readable before you have finished opening the app.
Service history, fuel entries and documents are keyed to the chassis number, not to your account — so the record follows the car. Ownership transfers go through a review step with fraud protection, so the next owner inherits the history rather than starting blank.
Kotlin Multiplatform with a Compose Multiplatform interface, SQLDelight for the offline database, Firestore for sync between devices. The business logic is written once; only the camera, the biometrics and the notification plumbing are platform-specific.
By the numbers
Build something similar
Motorix took one codebase and shipped to both stores. If you have a product that needs to exist on Android and iOS without paying for two teams, tell us the shape of it.