A LITTLE CONTEXT
Parking is a very physical problem: a driver needs a particular space, in a particular place, for a particular amount of time. The software has to turn that uncertainty into a clear arrangement.
Parking Buddy connects the driver’s booking journey with the owner’s availability and confirmation workflow. It is a marketplace with two different everyday jobs: finding somewhere to park and managing spaces that other people can use.
Make the choice specific.
A driver chooses a property, arrival time, duration, and an individual parking space. The product shows the pricing before they move into the reservation flow. That detail matters: the user should know what they are selecting, rather than being silently assigned a different slot.
Availability has to make sense for both sides. The driver sees the options they can book; the owner has calendar tools and private blocks to keep their own commitments reflected in the system.
Keep payment and confirmation honest.
The reservation flow holds a space while the driver pays the owner directly and uploads a receipt. Depending on the space’s settings, the owner reviews the receipt or the booking confirms automatically after upload. The driver then receives a parking pass.
A receipt upload is not bank verification. Keeping those states separate makes the product clearer: there is a difference between choosing a space, submitting proof of payment, and receiving confirmation. The interface needs to show where the booking actually stands.
The owner needs a product too.
A marketplace cannot stop at the customer checkout. Owners need to review bookings, maintain availability, and block time when a space is not available. Property management adds an approval layer where the building needs oversight.
Those tools turn the booking page into an operating system for the service. The driver-facing flow can remain focused because the owner and property-management workflows have their own places to handle the details.
A small interaction, a complete application.
Parking Buddy uses React and TypeScript with Cloudflare Workers and D1. Private R2 storage supports receipt handling. The architecture covers the public experience, application data, and files that should not become public assets.
This project captures my move toward building complete tools with AI: designing a useful flow, implementing the rules behind it, and carrying the idea through to a working application. The satisfying part is making the complicated coordination feel ordinary.
Choose the space. Know the price. Know where you stand.
WHAT’S UNDERNEATH
Tools behind the experience.
- React
- TypeScript
- Cloudflare Workers
- D1
- R2