The place that remembers the bike.
A motorcycle app built for Lebanon, 961 is the country code. Rides are not achievements here, they are data about the bike: distance moves the odometer, the odometer says what service is due, and the app finds the part and the mechanic.
- Sep 2026Started
- 8Feature modules
- 7Core packages
- 14Designed screens
Founder and product developer
My own product. I wrote the product doc and the master plan, designed the fourteen screens and set up the app as a modular Flutter workspace so each feature can grow on its own.
- Product thinking: one loop from ride to service to part to mechanic
- Fourteen screens from onboarding to group rides
- Modular Flutter workspace: eight features, seven core packages
- Mapbox map, live location and ride tracking on a real iPhone
The loop
Four features, one system. Pull any one out and the others get worse.
- 1You ride
- 2Distance recorded
- 3Odometer moves
- 4Service falls due
- 5Find the part and the mechanic
- 6Log the work
- 7The schedule resets
The screens
From the design handoff.

Home 
Garage: the bike profile 
Live ride tracking 
Ride summary 
Maintenance, due by distance 
Marketplace: parts and shops 
Road alerts: potholes, closures, flooding 
Group rides
What it does
- 01
Ride tracking
GPS recording with the arithmetic done honestly: distance summed between filtered fixes, noisy fixes thrown away, then distance, duration and average speed.
- 02
Garage
Each bike with its profile and odometer, starting with a Yamaha R3.
- 03
Maintenance
Service intervals driven by the odometer, so the app knows the chain needs adjusting in 900 km.
- 04
Marketplace
Categories, shops and products, so the part is findable.
- 05
Road alerts
Riders report potholes, closures and flooding nobody else publishes.
- 06
Group rides and SOS
Planned rides together, with an SOS plan written for when something goes wrong.
Stack
- App
- Flutter 3.38 workspace, provider for state.
- Map
- Mapbox with a custom Studio style.
- Storage
- Local on the device, backend planned.