Projects 08 / 11
Garajá
Vehicle maintenance for a household or a small fleet
Centralizes maintenance, refueling, documents and costs per vehicle. Designed for records made at the gas station or the garage: works offline, accepts backdated entries and syncs once the connection returns.
Overview
Garajá brings together everything a car costs: refueling, maintenance, expenses, documents and mileage, per vehicle, for a household or a small fleet. The dashboard answers two questions right away — what is due soon and how much each vehicle costs per kilometer.
Entries happen at the gas station or the shop, often with no signal, so the app is offline-first: it stores on the device, accepts backdated entries and syncs when the connection returns. The .NET 10 API is the shared contract for the React Native app and the React web panel, with attachments stored on Cloudflare R2.
Features
What the system does
-
A dashboard of what's due and what it costs
Last 12 months spending, cost per kilometer, kilometers driven, maintenance and document alerts, and spending per month and per vehicle.
-
Refueling and fuel economy
Liters, price, fuel, station and full tank. Fuel economy in km/l is computed between fill-ups and cost per km comes from everything the vehicle cost.
-
Maintenance plan
Rules by mileage and by time (oil, filters, alignment, timing belt, battery) with last and next service and a warning before it's due.
-
Maintenance, expenses and documents
Parts and labor per shop, tolls, car washes, vehicle tax, licensing, fines, registration and insurance with expiry alerts.
-
Attachments and notes
Photos and PDFs organized in folders, a full-screen viewer in the app and pinned notes per vehicle.
-
Shared fleet
Invite other members, owner and member roles, and the same history for the whole household or company.
Screens
Inside the system
Screens show fictional data generated for demonstration.
Stack
How it was built
- Mobile
- React NativeExpo SDK 58Expo Routerexpo-sqliteNativeWindTanStack QueryZustand
- Frontend
- ReactTypeScriptTailwind
- Backend
- C#.NET 10ASP.NET Core Minimal APIsEF Core 10JWTOpenAPI + Scalar
- Data
- PostgreSQL 18Cloudflare R2
- Infra & DevOps
- DockerCaddyxUnit v3Testcontainers
Behind the scenes
Technical challenges
-
Offline-first with backdated entries
Every record is born on the device with a GUID v7 and enters a sync queue. Since yesterday's fill-up can be logged after today's, the API validates odometer chronology against neighboring records.
-
Fleet isolation everywhere
Every table carries the fleet, EF Core global filters restrict every query and a SaveChanges guard prevents writing outside the scope. Routes are closed by default.
-
Uploads that actually work in Expo
Expo's fetch rejected files in FormData and no attachment reached the server. Uploads moved to XMLHttpRequest, with the file name decoded in the API and Wi-Fi-only uploads when the user prefers.
-
Costs that don't count twice
A document and an expense can't record the same payment, or cost per kilometer doubles. The model separates what is a deadline (document) from what is money (expense).
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