GarageDex

The "Duolingo of auto repair", in pixel art

A mobile game that teaches automotive diagnostic reasoning. The player runs a repair shop, reads symptoms, forms hypotheses and finds the root cause in daily challenges based on real cases.

Platforms
Mobile · Game
Year
2026
Status
In development
Role
Game design, back and front

GarageDex teaches you to think like a mechanic. The player owns a pixel-art repair shop and gets real cars with symptoms reported by the customer. The goal isn't to take everything apart, but to diagnose: pick the right test, find the cause and only then repair.

Every correct diagnosis unlocks a problem in the GarageDex, the collection of faults for each car model. Energy that recharges over time, daily streaks, trophies, per-workbench specializations and repairs that take real time build the daily habit of an app like Duolingo.

What the system does

  1. Diagnosis instead of trial and error

    The customer reports the symptom and the player chooses the next step among plausible options. Accuracy weighs on the reward.

  2. Real cars and faults

    Nine vehicles from five makers, nine engines, 66 common and chronic problems, 79 actions and 58 tools, with hidden problems that only show up for those who investigate.

  3. The GarageDex collection

    Each vehicle has its own list of problems to discover, with progress per model and per engine.

  4. A shop that grows

    Specialty workbenches, tools, lifts and parking spots bought with the money from each job, unlocking harder faults.

  5. Timed repairs

    Repairs run asynchronously and finish even with the app closed; when the player returns, finished work is waiting.

  6. Trophies, levels and daily streak

    30 trophies with bronze, silver and gold tiers, XP per specialization, reputation and a reward for every new day played.

How it was built

Frontend
Vue 3Quasar 2Piniavue-i18nPixel art
Backend
Laravel 13PHP 8.4SanctumPest
Data
PostgreSQL 17

Technical challenges

  1. A fair diagnostic engine

    Options mix the correct actions for problems not yet found with distractors, and there's always at least one right answer. When nothing is left to discover, the question disappears instead of making the player burn energy for nothing.

  2. Game rules on the server

    Energy, recharge, money, XP and repair completion are computed by the API, not the app. That prevents cheating and lets time pass with the game closed.

  3. Trophies derived from what happened

    The 30 trophies have no triggers scattered through the code: a service computes metrics from jobs, discoveries and purchases and advances tiers, awarding each achievement only once.

  4. Specification before code

    The project followed SDD and TDD: vision, scope, decisions and domain model documented, and the backend covered by Pest tests before any screen existed.

Need something
like this?

Tell me the idea or the problem. I help shape the solution and build it from the API to the app.

Let's talk