Builder Passport
@fatou_designs
Fatou Diallo
Product designer · learning to code
1 followers 1 following Dakar, Senegal
Designer moving into product. Sharing portfolio critiques and UX notes for African apps.
Execution Reputation
Proof from projects, collaboration, challenges, and endorsements.
Posts
Looking for two people to poke holes in my portfolio site
I've rebuilt my portfolio three times and I think I'm too close to it to see what's actually confusing. Looking for two people, ideally one designer and one developer, to go through it and tell me honestly where you get lost or bored. Happy to return the favor on your own portfolio afterward.
Would love blunt feedback on this checkout screen
Third iteration of a checkout flow for a personal project and I keep going back and forth on whether the payment method selection should be a dropdown or visible buttons. Please be blunt, I'd rather hear it's wrong now than after I build ten more screens on top of a bad decision. Screens attached in the reply.
Developers keep misreading my spacing, how do you hand off designs
I export images and write notes in the file, but the built version always ends up with slightly wrong spacing and font sizes. I don't know if the problem is my file organisation or how I'm communicating the specs. What has actually worked for people handing off Figma files to developers who aren't full time frontend?
What small, realistic things have people actually gotten paid for as beginners
Not looking for a get-rich story, just realistic examples. I keep seeing advice to 'monetise your skills' with no specifics underneath it. What has actually worked for people here as a first small paid thing, a landing page, a logo, cleaning up someone's spreadsheet, tidying documentation, that kind of scale?
Translating my own Figma file into HTML taught me a lot
As a designer learning to code, I decided to build the HTML and CSS for a screen I designed myself instead of using a random tutorial project. It exposed a lot of spacing decisions I never questioned as a designer, values that looked fine in Figma but felt awkward once they became real CSS. I understand my own design files better now than I did before I could code.
Redesigned the onboarding flow for a local savings app concept
This is a personal project, not a real client, but I wanted to practice designing for a genuinely local use case, group savings groups that already exist informally here. Went through four rounds of simplifying the sign-up flow after realising my first version assumed everyone already understood the group savings concept. Sharing screens in case it's useful for anyone designing for similar informal finance systems.
Should pricing be the same for someone billing in dollars and someone billing in naira
A tool I use charges the same fifteen dollars everywhere, which is nothing for a client billing in euros and a real decision for someone earning in a weaker local currency. Purchasing power parity pricing exists for exactly this reason, but I've also seen it get abused by people who can clearly afford the standard rate. How should something like this be handled fairly without either underpricing or gatekeeping unfairly?
Building a tiny design system taught me more than any course
I set myself a small challenge of defining just five colors, three text sizes, and consistent spacing for a personal project instead of eyeballing every screen. It forced decisions I usually postponed and made every new screen faster to design after that. A design system doesn't need to be big to be useful.
Proof of work
No projects yet
Featured work, demos, and outcomes will show here.
Activity
Certificates, challenges, and profile milestones.
No public activity yet
Course completions and milestones will show here when shared.
Skills & stack
Challenges
Leaderboards →Need help with Builder Passport?
- What is the Builder Passport?
- What is reputation on Africoders?
- How do recruiters hire on Africoders?
Ask Aurora