A booking web app for a family appliance-repair business in the GTA, built on Base44 (a low-code platform). I configured and customized the app, fixed its logic, wired the booking and notification flows, and hardened it for production — then kept it running while the family handles the repairs.
Below is what's actually inside — the work that turned a basic site into a working booking tool a real business runs on. Every piece was tested end-to-end before going live.
Click into the live site to see the front end — here's what I configured, fixed and built behind it.
Fixed a booking-display bug so the calendar shows every booking for a date instead of only the first one, and ran bulk status clean-up on stale pending requests so the schedule reflects reality.
Wired the notification flow end-to-end — customers get booking confirmations and the assigned technician is alerted automatically, so nothing falls through the cracks.
Locked the app down: row-level security, request rate limiting, authentication guards on protected routes, and secrets moved into environment variables instead of sitting in code.
Rewrote the service worker to a network-first strategy, so the app loads fresh content reliably and still behaves like an installable progressive web app.
Restructured the gallery into clear "Our Services" and "Recent Work" sections so visitors immediately understand what's offered and see proof of past jobs.
Configured the custom domain and DNS, and set up the technician account so the right person receives and works the incoming jobs.
I don't push to production on hope. Each flow was checked end-to-end, and everything passed before it went live.