Every appointment was booked by phone or text, which meant interruptions during jobs and a calendar that only lived in the owner's head.
Back to all projects
[ Case study ]
Sanchez Truck Services
Online scheduling for a family member's semi-truck greasing business, replacing phone calls and texts with bookings the owner can manage himself.
- Role
- Design, build, maintain
- Client
- Family business
- Stack
- Firebase Auth, Firestore, GitHub Pages
- Code
- GitHub repo
The problem
What I built
- Customer accounts with email and password sign-in and email verification, through Firebase Authentication
- Booking stored in Firestore, so appointments are saved and checked against what's already taken
- Blocked dates the owner can set for days he isn't working
- An owner panel to see and manage upcoming appointments
- Free hosting on GitHub Pages
Why this stack
Firebase handles sign-in and data storage without a server for me to run or patch, and its free tier covers a small business easily. That kept the cost at zero and the maintenance low, which matters when I'm the one supporting it.
What I learned
Building sign-in and data access for a real customer means thinking about who can read and change each record, not just whether the page works.