Fuel Prices, Mapped
Year: 2024A consumer app for finding the cheapest fuel nearby in Germany, rebuilt around a live map. Design system, product and front-end, shipped end-to-end and solo.
- A consumer app for finding the cheapest fuel nearby in Germany, built as a side project in my own time.
- Built the design system first, so a full redesign stays consistent and every new view is cheap to ship.
- Coded the production front-end with AI, on the HERE Maps API.
- A live map where the cheapest station in view turns green and stations cluster as you zoom.
Context
An existing German service for comparing fuel prices needed a redesign and a rebuild.
The cheapest fuel nearby
Anyone uses it to find the cheapest place to fill up.
All of Germany
Every station in range, on one map.
A side project
Designed and built in my own time.
Problem
10
year-old design
Outdated, and built on Google Maps.
Thousands of stations
Across Germany, they would bury the map.
My role
Solo and end to end: designer and engineer in the same loop.
Design system
Built first, before any screen.
Product design
The map experience, from search to the one station you pick.
Front-end
Coded with AI on the HERE Maps API and shipped to production.
Process
System first
I built the system before the screens, so a full redesign stays consistent and every new view is cheap to ship.
One loop, no handoff
I coded the live map myself on the HERE Maps API, so design decisions met the real map straight away.
Solution
The map is the product
- Challenge
- People come for one answer: where to fill up nearby.
- Solution
- The whole experience is a live HERE map of every station in range. Search, fuel type and radius narrow it down to one personal decision.
The answer finds you
- Challenge
- In a field of price pins, every number asks to be read.
- Solution
- The cheapest pin in view turns green, so you see where to go before you read a single number.
Density, made legible
- Challenge
- Thousands of stations across Germany would bury the map.
- Solution
- Stations collapse into counted clusters that break apart as you zoom: a problem solved in design and code at once.
Outcome
Shipped solo, from design to production code.
The interface and the production front-end, both mine.
One system under every view.
Rebuilt on a design system, so the redesign stays consistent and cheap to extend.
What I learned
Start with the system
On a side project with limited hours, the design system first made every new view cheap to ship.
Design and code in one loop
Building the front-end myself with AI meant nothing was lost in a handoff.