I’ve been trying this “vibe-prototyping” approach recently and I’m honestly a bit surprised by the results. In my last side project I was building a simple habit tracker and instead of planning everything in docs, I just started shaping rough screens with AI and adjusting based on how it felt when I interacted with it. What surprised me most was how quickly I started rejecting ideas that looked good in theory but felt wrong in practice once I could click through them. I read something similar here and it made me think this might be more than just a quick shortcut. Still, I’m not sure if this scales beyond small prototypes or if it becomes messy in larger teams where too many people iterate at once.
9 Views
I’m not really in development, I’m more on the operations side, but I still end up sitting in product discussions quite often. From what I’ve seen, teams tend to struggle more with explaining ideas than actually building small things, so this approach sounds like it could reduce a lot of misunderstandings. At the same time I wonder how teams keep long-term clarity if everything starts as quick experiments, because without structure it feels like things could drift in different directions. Still, it’s interesting how much faster people align once they can actually see and interact with something instead of just talking about it.