Why that button? Why there?
Every screen you use is a pile of decisions. This is where I take the pile apart, out loud, so anyone can follow the thinking.
What this is
Why That Product is a place to learn how products get made by looking closely at ones you already know. I make short videos and written notes in four flavors: teardowns, quick verdicts on whether people would pay, diaries from my user conversations, and interview practice.
I don't pretend to have the inside story. I look at what's on the screen, make an honest guess about the decision behind it, and say what I'd test to find out if I'm right.
Who it's for
- People who are curious how apps they use every day got to be the way they are.
- People preparing for product interviews who are tired of memorizing frameworks.
- Builders and founders who know they should talk to users and don't know where to begin.
- Anyone who has ever stared at a screen and wondered why that button is there.
Ground rules
- I say what I see first, then I say what I'm guessing. They never get blended.
- I stay kind to the people who built it. They were working with constraints I can't see.
- If I get something wrong, I say so in the next video and show what changed my mind.
- No fake authority. I'm figuring this out in public, and you're welcome to argue with me.
What this isn't
It isn't advice from a famous product leader, and it isn't a polished course. Deeper walkthroughs may come later, and what you tell me now decides what they cover. If you're stuck on something, say so on the connect page.
A bit about me
I'm Smrity, an artist and dreamer at heart who got hooked on how products get made. I sketch, I build small things, and I ask a lot of questions. Here, I turn that habit into something you can watch and learn from. You'll see me get things wrong, and that's on purpose.