Client work2025Garaj
Vehicle specs, comparison, a 1v1 quiz and driving tests.
- Project
- Carage
- Our role
- Mobile development · Admin panel · Release
- Duration
- 3 months
01 / Behind the product
A real need. A considered solution.
Challenge
Vehicle spec data is scattered and hard to compare: dozens of attributes across brand, series, model and year, and the same body generation carries the same specs for years. The client wanted to enter and manage that data themselves, with a gamified layer on top to keep users around.
Approach
The catalogue lives in Firestore and is entered from a Next.js admin panel: brand → series → model → year → specs in ten categories; spec categories and home-screen sections are edited there too. After client feedback a year range became a single record, so 2010–2020 is entered once. On mobile, side-by-side comparison highlights the better value.
The 1v1 quiz runs six league families × three tiers with live matchmaking; every match decision happens in Cloud Functions and the client only calls and listens to the match document. The performance test measures 0–100 / 0–200 by GPS and the reaction test measures response time with drag-strip lights; those two stay on-device and, by security rule, write only to the user’s own document.
Result
Version 1.0.4 was delivered with the mobile app and the admin panel; delivery, release and Firebase notes went to the client as PDFs. Car / SUV / commercial filters, the ice theme and AdMob integration are in the product.
02 / Inside the product
The experience, on screen.
Open a screen to explore the details.02 images
03 / Scope & details
The details make the experience.
- 01
Brand → series → model → year → specs in ten categories
- 02
Side-by-side comparison of two vehicles
- 03
1v1 quiz: six leagues × three tiers, decisions made in Cloud Functions
- 04
GPS 0–100 / 0–200 performance test and a reaction test
- 05
Catalogue entered from the admin panel; year ranges as one record
Technology
INSIDE THE PRODUCT
The engineering behind the interface.
Systems we built and concrete problems we addressed in this project.
Match decisions on the server
The quiz client only calls and listens to the match document live; matchmaking, questions, timing and scoring are all decided in Cloud Functions. Reaction and performance tests keep the measurement on device and, by the request.auth.uid == uid rule, write only to the user’s own document.
A year range is one record
The year field accepted only a number and a range created a separate vehicle per year: 2010–2020 meant eleven records and eleven rounds of data entry. An optional range field was added to modelYears; specs are entered once and cover the whole span.
The catalogue flow
Brand → series → model → year → collapsible specs in ten categories; comparing two vehicles highlights the better value. The car / SUV / commercial filter and home-screen sections come from panel-managed content.
Your idea could be next.
What could we build for you?
From a first release to a growing platform. Let’s plan the design, development and launch together.
From Türkiye to the US, UK, Australia and everywhere in between.