Operations · React Native + PHP · Sold to clients
A register book, rebuilt as three taps on a phone.
A staff-facing app for parking lots: log a vehicle in or out, price it by category, and pull a real earnings report for any date range — built for the gate, not adapted from a generic form builder.
How a vehicle moves through it
From gate to logged, in four steps.
Vehicle arrives
Staff open the check-in screen — no login sharing, each shift is its own account.
Category selected
Bike, car, or SUV — priced automatically from rates an admin set up once.
Entry logged
Plate and time recorded as one record, not a slip of paper to be typed up later.
Checked out
Exit closes the same record — duration and category are already there, nothing re-entered.
The problem
Most "parking software" is a spreadsheet wearing a login screen.
A parking desk doesn't need more fields to fill in — it needs fewer. The actual requirement was a check-in flow fast enough to survive a line of cars forming behind the one currently at the gate, with pricing that doesn't need a calculator and a shift log that doesn't need one shared password.
What it does
Built around the gate, not around a spreadsheet.
Check-in / check-out flow
A vehicle's full stay — entry time, exit time, category — logged as one record, not two disconnected data entries matched up by hand later.
Vehicle categories
Bikes, cars, SUVs — priced and tracked separately, set up once by an admin and applied automatically at check-in.
Staff & access
Individual staff logins with a super-user settings tier — so a shift change doesn't mean sharing one password around.
Earnings & reports
Pick a date range and get total earnings, vehicles checked out, and a per-vehicle breakdown with amount charged — not just a count of cars.
Why it holds up
Built for the gate, not a form builder
Every screen exists because one specific step at the gate needed it — check-in, check-out, categories, staff — not a generic CRUD app with parking-shaped fields.
No shared logins
Each staff member has their own account, with a super-user tier for whoever manages pricing and categories — so a shift log means something.
Built and supported by one person
Mobile app, backend, and deployment all sit with the person who wrote the code — no gap between "who built it" and "who answers when it breaks."
Want the real build story — the decisions behind the check-in flow?
Read the full case study