Every guy I know has the same problem on her birthday: he wants to get her flowers, he has no idea which ones, and he doesn't want to ask, because then it's not a surprise.

So he guesses. Sends the florist twenty DMs. Ends up with red roses she politely pretends to love. 🌹

I built Bloom for Her to fix this.

He sets a budget, a date and an address, then gets a link and sends it to her. She opens it and sees only bouquets in his range, with the prices hidden, so she picks what she actually wants, not what feels "affordable". He gets a notification, confirms and pays in one tap. The florist gets a complete order with the bouquet, her wishes ("no lilies please"), delivery slot and card text. No DMs, no guessing.

How I built it I'm a UX/UI designer who also writes Flutter, so I skipped the usual "design → hope the dev gets it" step: → wireframes and high-fi screens for 3 roles: him, her, the florist → a design system: Urbanist only, no bold, one dusty-rose accent, borderless inputs → built in @Lovable from my screens: React + Supabase, realtime order status, an admin panel for the florist with auth → AI-generated bouquet photography, so the catalog looks like a real shop

Time: ~10 hours, from "hmm, what about flowers?" to a working product.

What I learned: the hardest part wasn't the code. It was deciding what she shouldn't see. Hiding the price turned out to be the whole product.

Demo below 👇 Concept business — Hackney, London (demo details).

@Lovable

Hiding the price being the whole product is a great insight. Ten hours well spent.