Inspiration Most small barbershops and salons I talk to still take bookings by phone or walk-in, and they lose customers to missed calls and no-shows. I wanted to build them a booking tool that feels like a real product, not a boring form. Kiroween gave me the perfect excuse to make it haunting, so GhostDesk was born: a booking desk run by ghosts.
What it does GhostDesk lets customers browse services and book an appointment online in under a minute, and lets owners manage staff, time slots, and no-shows from one dashboard. Booked slots rise like spirits, empty slots glow, and overdue bookings turn ghostly, so the whole day is readable at a glance. It is built for barbershops and salons, but the booking flow works for any small service business.
How we built it I built GhostDesk with Kiro using its spec-driven workflow: I wrote the spec first, then let Kiro break it into tasks and build it step by step, with steering docs keeping the design and rules consistent. The stack is Next.js, TypeScript, Tailwind CSS, and PostgreSQL. The midnight UI uses deep blacks, fog, candle-glow, and violet accents, with every spooky element tied to a real function instead of decoration.
Challenges we ran into The hardest part was making a dark, haunting UI that stays usable: too much fog or glow and the booking times become hard to read. I also had to handle double-bookings cleanly, so two customers can never grab the same slot, and keep the owner dashboard simple enough for a non-technical shop owner. Kiro's spec helped here — when a change broke a rule, the spec caught it before I shipped it.
Accomplishments that we're proud of I'm proud of the UI most: it is genuinely haunting and polished, but the spookiness actually helps you use the app. I'm also proud of the booking flow itself — a customer can go from landing page to confirmed booking without an account or a phone call. And the whole app was built spec-first, so the code stayed clean and maintainable instead of turning into a rushed hackathon mess.
What we learned I learned that writing the spec before the code saves more time than it costs, especially when an AI agent is doing the building. I also learned how much UI matters: the same booking feature feels completely different when the design has a clear mood and every visual choice has a purpose. And I learned to test the dark theme on real screens early, because glow and contrast behave very differently on mobile.
What's next for GhostDesk Next I want to add SMS and WhatsApp reminders to cut no-shows, online payments and deposits, and a multi-branch view for owners with more than one shop. I also want a public booking page each shop can share as its own mini-website, so a salon with no website at all can start taking online bookings the same day.
Built With
- gsap
- next.js
- react
- tailwind-css
- typescript
- vercel