The whole cycle got faster and clearer, and more of it was right the first time. Design, product, and engineering got time back, and fewer missed states turned into rework.
Context
Reviews kept missing the messy screens.
Reviews jumped between screenshots, tickets, and the path where everything goes right. Empty screens, error messages, and layouts that broke on a phone slipped through until QA found them.
Those states were already in the prototype. Getting to one meant remembering the clicks that lead there, and a review rarely covered every path.
I built a tool that reads the prototype and puts those screens and states on the left. You move through them, and picking one takes you straight there.
Once you’re on a state, you can compare it to what’s in production and check it on different screen sizes. When the prototype changes, the navigation updates with it.
The cycle got faster for design, product, and engineering. More of the work was right the first time, and fewer states slipped through to QA.
Loading prototype
Less time, a faster cycle. Design, product, and engineering spent less time finding a state and walking back through the paths that get you there.
Missed states caught in review. Empty screens, failures, and broken layouts showed up in review, before they reached production.
Right the first time, less rework. More of the work was right the first time, so less of it came back after it left design.