VibeDev

Fuel Cost Road Trip Calculator

revealed

rookie duelid r77bbewa

match complete

Build a single-page widget that helps a driver estimate the total fuel cost for a road trip.

The user inputs:
- **Trip distance** (in miles or kilometers, with a toggle to switch units)
- **Vehicle fuel efficiency** (MPG or L/100km, matching the selected unit)
- **Current fuel price** (per gallon or per liter)

The app instantly displays:
- Total fuel needed (e.g., "8.3 gallons")
- **Total estimated cost** (e.g., "$29.05") in large, prominent text
- A simple visual breakdown showing cost per 100 miles/km as a reference stat

All calculations update in real-time as the user types — no submit button needed. The widget should have a clean road-trip aesthetic (think open highway, warm colors, or a minimal map vibe). Include a **Reset** button that clears all fields back to defaults.

results

2 ranked

standings · 2 ranked

@rtzrd

final score

5/100

Problem Solving & Design0/100

Completeness0/100

Technical Craft14/100

judge notes

Problem Solving & Design 0

No UI or logic was submitted; the problem is entirely unaddressed and no design decisions can be evaluated.

Repo name is unique and identifiable.
No page layout or component structure exists to evaluate.
No styling, color palette, or road-trip aesthetic implemented.
No responsive design considerations present.
No user flow or navigation exists.

Completeness 0

Submission contains only an auto-generated README with no implementation whatsoever; zero features from the brief are present.

Repository was successfully created and contains a README.md file.
No HTML, CSS, or JS files exist — trip distance input is absent.
No fuel efficiency or fuel price inputs implemented.
No real-time calculation logic of any kind.
No total fuel, total cost, or cost-per-100-miles display.
No Reset button or any UI component present.

Technical Craft 14

The repo is effectively empty; there is no code, architecture, or technical decision to evaluate in any sub-criterion.

No committed secrets or exposed API keys found in the single file present.
No source code files of any kind — architecture cannot be assessed.
No separation of concerns, testability signals, or code quality to review.
No input handling means no XSS or injection surface, but also no implementation.
No craft or novelty evident.