I started the SeneGence checkout redesign by looking at where people stopped. The behavior data and stakeholder feedback pointed to the same place. Navigation was confusing, mobile and desktop didn’t match, and checkout required an account before anyone could pay. I took the checkout first. Dropping the account requirement was the biggest change, and the rest was making each step clear about what was coming. The video is me going through the mobile checkout as it works now. It’s short, which is the point. The full redesign ran six months and ended up with 80K+ conversions and over $7M in revenue. I was the designer on it from problem definition through delivery, working with engineering and the business team. If you’re stuck on a conversion problem, start by finding the exact screen where people leave. Redesign that one first.

2

31

I've tried learning React a few times. Always hit the same wall. The tutorials made sense while I was watching them but then I'd close the video and have no idea where to start on my own. Scrimba is different because the lesson is the code editor. You're not watching someone build in one window while you try to copy it in another. You click inside what they're working on mid-lesson and write directly in it. I'm still early in it but I'm further along than I've ever gotten before. For designers trying to bridge design and code, it's the most useful format I've found. scrimba.com (http://scrimba.com)

0

85

Every product page decision has a job to do before someone ever reaches checkout. On the SeneGence PDP, the job was simple to state and hard to execute: help someone choose a shade with confidence. That meant building the color swatch grid as the primary interaction, not a secondary detail, with limited edition tags called out clearly so nobody's disappointed after checkout. Related shades and complementary products show up right below, so discovery doesn't dead-end at one product. On the listing page, filters had to hold up across dozens of SKUs. Mobile users get a filter drawer with chips for active selections. Nothing gets buried behind a menu they'll forget to check. Case study here: patlopes.com/case/senegence-redesign

2

130

I've been sending a lot of outreach messages lately as part of my job search, and pretty quickly ran into the same wall every time. Writing a good, personalized message was never the problem. The problem was everything before it: finding the right contact, pulling context on the role or company, checking if I'd already reached out, then logging it somewhere so I wouldn't lose track. There was a lot of repetitive work standing between me and writing the message itself. So I started building a small dashboard (React, Vite, deployed on Vercel) to handle the deterministic stuff. It looks up contacts, pulls the context I need, and tracks everything in Notion automatically. I pretty much just do the writing. Still early and still just for me, but it's already saved a chunk of time I used to burn on busywork instead of actually reaching out to people. #ProductDesign #BuildInPublic #JobSearch

9

13

680

Patrick Lopes

Senior Product Designer + Frontend Developer | AI-Assisted