1/
From Figma to live. π
Lulu Artistry is now live, and it's my first live project and my first paid project as a Product Designer.
A thread on the journey π§΅
2/
What it is: a beauty e-commerce and service booking platform.
Customers shop products and book services in one place.
5/
AI is fast at generating options.
Knowing which problem you're generating them for is still on me.
6/
Building a product and want it to actually hold together? That's what I do. Open to new projects DM me.
1/
I generated two full design systems this week.
AI did the heavy lifting.
Here's the one part it still couldn't do. π§΅
2/
By the time I open an AI UI tool, the thinking is already done: problem statement, MVP, sitemap, user flow.
I turn that into a prompt.
4/
Research showed verified-seller status and reviews as the top trust drivers.
So the forest green and the verified seller badge aren't decoration they're the answer to that finding.
The tool hands back colors, typography, buttons, status tags.
3/
What it can't decide: why a color belongs there.
On a social-commerce project for Nigerian sellers, the brief was "make buyers trust a stranger's storefront enough to pay before delivery" not "make it look clean."
and real business needs.
6/
Try it live: https://t.co/p1NPJ2G4bn
I'd love your feedback. What would you improve?
I'm also open to new product design projects. My DMs are open. π
#ProductDesign#UIUX#Figma
1/
From Figma to live. π
Lulu Artistry is now live, and it's my first live project and my first paid project as a Product Designer.
A thread on the journey π§΅
2/
What it is: a beauty e-commerce and service booking platform.
Customers shop products and book services in one place.
4/
What I focused on:
β’ Clear flows for customers, from browsing to booking
β’ Responsive design across web and mobile
β’ A dashboard that keeps day-to-day work simple for the business
5/
My biggest lesson:
Design doesn't end in Figma. It has to survive development, real users
The business owner manages everything from an admin dashboard.
3/
I was part of the development last year. This year, it's live.
Seeing screens I designed in Figma become a working product is a different feeling.
A clinic's entire booking system was a WhatsApp inbox.
Bookings got buried. Nobody could match payments to patients.
So I designed the fix. Full prototype walkthrough π§΅
1/ Patients get a consultation-first booking flow with fees shown upfront. No price surprise halfway through.
5/ I designed the error states too: slot taken mid-booking, unmatched payment, two staff on one booking.
6/ It's responsive, because most patients will book from a phone. Now with my developer for the build.
A screen is a picture. A product still works when things go wrong.
2/ Payment is bank transfer, designed around how clients actually pay. No payment gateway needed.
3/ The clinic gets one dashboard for every booking, payment and patient record. No more scrolling WhatsApp.
4/ Staff join by invite only. No public sign-up anywhere.
1/
A friend wants to build an app "just like YouTube."
His teacher said no one can build it.
My reply wasn't "I can." It was a question. π§΅
2/
"What do you mean by just like YouTube?"
YouTube isn't a video player. It's uploads, processing, streaming, search, recommendations,
1/
A friend wants to build an app "just like YouTube."
His teacher said no one can build it.
My reply wasn't "I can." It was a question. π§΅
2/
"What do you mean by just like YouTube?"
YouTube isn't a video player. It's uploads, processing, streaming, search, recommendations,
low data playback. That's buildable.
4/
My process:
Problem β Users β Core value β User flow + sitemap β MVP β Design β Build β Test + iterate
Vibe coding speeds up the later steps. It doesn't replace the first ones.
moderation, security and monetization.
3/
So the teacher was half right: nobody builds YouTube on day one.
But "can't be built" is the wrong frame. The better question: what version should be built first?
Example: a video app for Nigerian skit creators with short uploads and