Vehicle importTaken over, rebuilt in Flutter and run
WAH app
iOS and Android app for buyers and dealers
Native Kotlin and Swift apps rebuilt in Flutter: one shared codebase for buyers and dealers, with ongoing iOS and Android releases.

The problem
Buyers and dealers needed one app for browsing, bidding at partner auctions, chatting and tracking orders.
The previous Kotlin and Swift apps meant maintaining two separate native implementations. They did not cover the dealer side.
What we built
- 01
From two native apps to one Flutter codebase
We took over the existing mobile product and rebuilt it in Flutter. Shared feature development and a common release process replaced separate Kotlin and Swift implementations.
- 02
The buyer side
Catalogue, bookmarks, auction access, chats, orders, a dealer directory with a map, QR codes and office locations.
- 03
The dealer side
A dashboard, contracts, documents, orders, vehicles and inquiries, and a customs-clearance estimate from photos of vehicle documents.
- 04
Design system and releases
Figma design tokens compiled into code, end-to-end flows for both sides in Maestro, and fastlane releases with notes from the changelog.
What runs now
We ship both stores from CI, run the end-to-end flows and keep the app on the shared catalogue API.
Facts
- Rebuild
- Kotlin and Swift replaced by one Flutter codebase for iOS and Android.
- Customs
- Dealers get a customs-clearance estimate from photos of vehicle documents.
- Auctions
- Access to European vehicle auction platforms inside the app.
- Testing
- Maestro end-to-end flows cover the buyer and dealer paths.
Screens
Related
Next step
Tell us where it is. A short call about what you have, what blocks launch and whether we are a fit.
A free 30-minute call to understand your product and agree the next step.








