Booking a fitting shouldn’t take more messages than the alteration itself.

Meet Tivora Atelier, a fictional clothing alterations studio in Bucharest. The problem: a solo owner spends too much time asking every customer the same questions and coordinating appointments by hand.

I designed and built a booking experience in @Lovable that takes a customer from “Can I book?” to a confirmed fitting. They share garment details, choose an available time and receive a confirmation email. They can add the fitting to their calendar or use a private link to manage it later.

On the other side, the owner has one view for appointments, garment notes and availability.

This is an exploratory demo, not a real booking service. The video walks through the customer and owner experiences in under a minute.

Explore the public project: https://tivoraatelier.lovable.app/

#lovablechallenge

Great job, Anca

🤔When applying to jobs, I often see requirements like “advanced Figma skills” or “using best practices, Auto Layout, components, variables, etc.”

Come on, this is the basics.🤷🏻‍♀️

As a designer with 10+ years of experience building SaaS web applications, I see these things as a foundation, not something that should even need to be asked about.

But since clients often want proof of these skills, I decided to write an article showing exactly how I organize a large SaaS web application in Figma.

I think it can be useful not only for clients, but also for experienced designers and teams.

And I’d be glad to hear about any practices you use that I didn’t mention.🙌