Oma: an end-to-end ordering system for a solo bakery in Madrid
Oma is a brand I designed for my mother's bakery, which makes this project especially personal. Like many solo owners, Verónica was losing hours every week to manual coordination, and her customers faced a barrier before they could even place an order: no clear catalogue, no visible availability, no simple way to commit.
This build closes that gap from both sides:
- For customers, ordering becomes self-serve. Products, quantities, pricing and available pickup times are clear from the start, and they can create an account with their email to manage their orders and repeat purchases.
- For the owner, everything she needs to prepare each day is in one view: production plan, pickups, shoplist, customer changes and the decisions that still require her judgement.
The result is an integrated solution that reduces friction for the customer and removes manual work for the business, while staying true to Oma's brand identity.
I already submitted my Lovable challenge but I decided to update the landing page and make it look a little bit better by introducing more images to make the page a little bit more interactive especially on the services section, which one do you like: the old one or the new one?
And somehow, almost one full day of those three went into the intro you see when the page first opens.
Not because it was necessary — mostly because I’ve wanted to try something like this for a long time.
Web design and development are far from my main field, so I kept putting this idea off. This challenge finally gave me a reason to test it properly — and seeing it actually work is ridiculously satisfying.
The video was converted into an image sequence and tied directly to scrolling on desktop and swiping on mobile, so the animation is controlled by the user as they move through the page.
Right now the project is already at Build 4.2.3.
The backend is working properly, the main mechanics are in place, but visually… there’s still a lot to redo. The current plan is to rebuild almost the entire visual layer before the final version.
I also found out today that Lovable reduced the number of prize spots quite significantly — apparently, there will only be 3 finalists.
That definitely makes the odds a little more painful 😅
But either way, I’m already getting a new portfolio case out of this project, and I’m finally experimenting with things I’ve wanted to build for a long time.
How’s everyone else doing?
Still working on your project, or have you already submitted it?
Or did you decide not to participate at all? If so, I’m curious — what made you skip it?
That intro effect looks sick! 🔥 By the way, I'm working on a car showroom project too, but not sure if I'll manage to finish and submit it on time. If luck is on my side, it’s going to be a really fun competition haha. Good luck!
FadeFlow: From “Can I book Saturday?” to “You’re booked.”
I built FadeFlow for Fade District, a fictional solo barbershop in Yaba, Lagos, run by Malik Adeyemi.
The problem is simple: a lot of bookings start with a message like:
“Can I get a haircut Saturday afternoon?”
From there, Malik has to ask for the service, check availability, reply with time options, create the booking, confirm it, collect the deposit, send reminders, and handle changes.
FadeFlow removes that back-and-forth.
Customers can choose a service, see available times, pay a ₦5,000 deposit, and confirm their appointment themselves.
And when they still message instead, FadeFlow turns the inquiry into a structured booking request. Malik can see what they want, send available times, and create the booking in one action.
Once it's booked, FadeFlow keeps everything connected: