ShipWithYuki (@ShipWithYuki) header
ShipWithYuki (@ShipWithYuki) profile picture

Product designer for early-stage founders Turning unclear ideas into build-ready experiences Founder - https://teapaw.org/t.co/vks6pRv9Eh Book a call ↓

Let's discuss your projects 👉
Joined January 2026
Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)Photo by ShipWithYuki (@ShipWithYuki)
Running Clarity Audits for early-stage founders this month. Written audit document, 3–5 days, starting from $150. Full details here 👇 drive.google.com/file/d/1UFl…
1
5
173
ShipWithYuki retweeted
The full breakdown of each decision is spread across weeks of posts. Go back through them if you want the “why” behind any specific screen.
3
1
2
50
ShipWithYuki retweeted
I deliberately made EchoCircle’s matching slower. Match Found → Skip / Let’s Talk 2 extra seconds gives users control before a stranger’s mic goes live. Speed isn’t always better UX.
1
1
3
62
ShipWithYuki retweeted
September dump funny how i got crazy content ideas of one project. Closing it today. Posting all screens
1
5
61
ShipWithYuki retweeted
I have about 15 things I want to do this week. Which is probably the problem 😂 Trying something different this week. Less trying to do everything, more actually getting shit done.
1
8
73
Most apps treat reactions as expressions. Gbagede treats them as power. Every tap shifts the score. My job was to make that feel obvious without a tutorial. This is what I do at ShipWithYuki I make complex ideas feel simple.
1
1
4
70
Most founders think they have a design problem. They don't. It's a clarity problem. In 30 minutes I can tell you exactly where your product is losing people. Here are the 5 questions I use 🧵.
2
3
87
Shipped ≠ done. Most MVPs don't fail because the product is bad. They stop because the founder ran out of energy trying to figure out what to fix next. That's the part nobody talks about.
1
5
36
I posted a full video breakdown of this project yesterday. These are the screens from a mental health platform I designed for healthcare workers in Canada. Every screen has a decision behind it. The video explains the thinking. Go watch it if you haven't 👇
I designed a mental health platform for healthcare workers. Full design process breakdown in the video. Not just what it looks like. Why it works. The thinking behind every screen decision 👇
2
4
82
I designed a mental health platform for healthcare workers. Full design process breakdown in the video. Not just what it looks like. Why it works. The thinking behind every screen decision 👇
1
4
1
14
178
Read this thread before you build your next feature. 👇
1
1
3
48
Working on something 👀 Fitness app. Customized to how you actually train. Screens below. Later this week I'm building this live with Claude Code. Designs to working prototype, on camera. Stay tuned.
2
2
6
60
Is this worth $1k? Full HRMS landing page. 2 days. Desktop and mobile. Anyone can make it look good. Not everyone can make it make sense. Landing pages like this start at $1k 👇
5
10
46
1
28
What does success look like for you at week 4? 👇
Why I ask founders what success looks like at week 4. Not week 1. Not at launch. Week 4 🧵.
4
68
Why I ask founders what success looks like at week 4. Not week 1. Not at launch. Week 4 🧵.
12
1
1
13
445
The fastest way to lose a user in the first 30 seconds? Make them think. Not about your product. About how to use it. That's not a design problem. That's a thinking problem.
1
2
9
92
1/ Most founders think they have a feature problem. Most of the time, it's actually an onboarding clarity problem. Here are 5 signs your onboarding is confusing users 🧵
10
1
1
12
279