Z-Maps Car
Roadmap
V1 works. What comes next, and why in that order.
Roadmap
What is being built, and in what order
The order is set by how much each item improves the accuracy of the speed warning — with OBD-II out of scope, that accuracy is the entire core of the app.
- V1Shipped
Working in a real car
Map, speed, speed limits, overspeed alerts and a Settings screen. Builds to ABI-split APKs, 46 unit tests passing.
- V1.1Shipped
Trip history, and correcting limits in the car
Trips written to SQLite with a history screen, speed limits correctable from the driving screen and remembered for next time, an adaptive icon, and keystore-based APK signing.
- V1.2In progress
More accurate road matching at stacked junctions
Flyovers above service roads remain a genuine weak point for road matching. It is the current piece of work, because matching the wrong road means reporting the wrong limit.
- V1.5Next
Better speed-limit data
Building tiles with Planetiler under a custom profile that carries the maxspeed tag, instead of inferring it. This is the single biggest improvement to what the app is actually worth.
- V2Planned
Maps and navigation
Turn-by-turn navigation via Valhalla or GraphHopper, offline coverage of the whole country with PMTiles, and place search.
- V3Planned
Community data
Speed-camera alerts, community-contributed speed limits, incident reporting, cloud sync, and a HUD mode that mirrors onto the windscreen.
Want to argue with the order?
If you are running the app in a real car, your feedback can change it.