Helping vehicle owners compare real-time fuel prices, locate nearby stations, and access emergency roadside assistance.
70%
Drivers skip price check
40%
Breakdowns preventable
3+
Target user segments
5
Core features designed


Fuel Buddy is a mobile app concept designed to solve three interconnected problems that vehicle owners face daily - unpredictable fuel prices, difficulty locating nearby stations, and lack of quick emergency roadside help. This was a solo concept project where I owned the full design process from research to final UI.
Role
Solo UI/UX Designer (End to End)
Timeline
4 Weeks - Concept Project
Platform
Mobile App (iOS & Android)
Tools
Figma · Notion · Pen & Paper
Fuel prices fluctuate daily, yet most vehicle owners have no easy way to compare prices before refueling. Beyond cost, finding a nearby station in an unfamiliar area and getting quick help during a breakdown are equally frustrating pain points with no unified solution.
70% of drivers refuel without checking prices, leading to unnecessary overspend on every fill.
Google Maps shows stations but not live prices. Users have to cross-reference multiple apps.
40% of breakdowns are preventable - but when they happen, drivers struggle to find quick help.
Fleet operators have no visibility into driver fueling behaviour or station price optimisation.
I conducted informal interviews with 5 vehicle owners - daily commuters, a fleet manager, and a delivery driver - to understand real frustrations around fueling.
"I never check prices - I just stop at the nearest station."
- Daily commuter, Chennai
"When my tyre burst on the highway, it took me 45 minutes to find help."
- IT professional, 32
"I manage 12 vehicles and have zero visibility into where my drivers refuel."
- Fleet manager
Manages 12 delivery vehicles. Monthly fuel spend: ₹80,000+
Reduce fuel costs & track driver refueling behaviour
No real-time price data, no driver accountability tools
Drives 40km/day. Refuels 2-3x per week.
Save money on fuel & get help fast during emergencies
Wastes time finding stations, panic during breakdowns
No single existing app combines all three core needs. This gap validated the opportunity for Fuel Buddy.
| Feature | Google Maps | PetrolPrices | Fuel Buddy |
|---|---|---|---|
| Real-time price comparison | |||
| Nearby station finder | |||
| Emergency roadside assistance | |||
| On-demand fuel delivery | |||
| Fleet management dashboard | |||
| Trip cost calculator | |||
| Crowdsourced price reporting |
I followed a structured design thinking approach - moving from broad ideation to focused execution through four phases.
Informal user interviews + competitive research to validate the problem space.
Who/What/How/When framework + user personas to anchor design decisions.
Divergent brainstorming across 4 idea categories, then converged to 5 core features.
Hand-drawn wireframes → Figma high-fidelity screens with component system.
I used divergent thinking to explore ideas across four categories before converging on the most valuable features.
From the brainstorming pool, I converged on 5 features that deliver maximum value with the highest user need and lowest implementation risk.
Users search and compare live prices across nearby stations. Saves money on every refuel.
Map-first interface showing closest stations with price overlays and distance. Built for unfamiliar areas.
Push notifications when prices drop or spike in the user's area. Helps users time their refuel.
One-tap access to puncture repair, towing, and oil refills with real-time ETA tracking.
Users enter destination and vehicle type - app estimates total fuel cost based on live prices en route.
Browse the designed screens of Fuel Buddy. Click on any screen slot to upload and preview your own high-fidelity product interface screens directly in the layout.
These three decisions were intentional and grounded in user behaviour.
Chose a map view as the default instead of a list because users in unfamiliar areas need spatial context first. A list requires mental mapping - the map is immediate.
Fuel price is displayed in large, high-contrast text on every station card. This removes friction from the core task - comparing prices at a glance.
Roadside assistance is accessible from a persistent bottom bar, not buried in a menu. In an emergency, users should not have to think - they need to tap once and get help.
With more time and real user testing, I would prioritise these next-phase features.
B2B view for fleet managers - track all vehicles, fuel spend per driver, and flag overpriced refueling. Unlocks a high-value commercial market segment.
"Prices in your area likely to rise tomorrow - refuel today to save ₹3/litre." Based on historical trend data. Low-effort, high-perceived-value feature.
Connect to the car's fuel sensor via OBD dongle - app auto-alerts when fuel is low and shows the nearest cheapest station. True proactive UX.
Not just emergencies - users can schedule morning fuel delivery to home or office. Think Swiggy model applied to fuel logistics.
I didn't set measurable goals at the start. Going forward, I'd define what success looks like - even rough proxies - before touching Figma.
I worked from secondary research and assumptions. Even 3 quick user interviews would have sharpened the problem definition significantly.
The fleet management use case emerged late. Identifying it earlier would have shaped core architecture decisions differently.
Hiring for something complex? Tell me what your team is trying to fix. I read every message.
Looking for a full-time product or enterprise design role, especially one with the messy, unglamorous problems in it.