Plumbline: bookings for a solo building engineer in Budapest. Built with @Lovable for the #lovablechallenge.
Réka checks flats before people buy them. But she's up in an attic when the phone rings, and every buyer has a deadline: the day they sign the deposit.
→ Book in 2 minutes, only times before the deposit deadline
→ The seller's agent confirms access with one tap. If they don't, everyone is warned 24 h ahead, not on the doorstep
→ A German WhatsApp at midnight? The AI drafts the reply with 3 free times. Prices and times come from tested code, never from the AI
→ English · German · Hungarian, real email notifications, and a demo clock to watch it all happen
Before → after: ~2 days → ~2 min to confirm · ~25 min → ~0 admin per booking · locked doors caught a day early
Built Gloss Instant Booking for the #lovablechallenge.
I created a booking experience for a fictional solo automobile detailing business in Austin where the owner was losing time to back-and-forth booking messages.
Really like how clearly you've framed the before vs. after workflow here. For a mobile detailing business, did you also account for travel time/location when determining availability?
Feels like that's where scheduling gets especially interesting once bookings start stacking up.
I have decided to create minimal friendly pet booking app MINTLEAF, in Lovable, user friendly simple and creative approach to collecting and solving major pet clinic problems in short time, both compatible as desktop app and mobile version.
Nice direction, especially taking it mobile-first too. Curious, does the booking flow capture the reason for the visit or any pet context before confirming?
Vet clinics are one of those cases where not every available slot is necessarily the right slot.