The Link That Does Not Change
The biggest change in how my design team works this year is a small one. We stopped reviewing screenshots and started reviewing live HTML prototypes.
The unlock is the hosting. Each prototype sits at a constant link that does not change when I re-upload. I push an update and the same URL serves the new version. No re-sharing, no latest_v3_final files, no Drive folders to dig through.
For the team that means feedback happens on the real thing: the actual tap, the actual transition, how a number animates as an order fills. Not a flat image of it.
- One link per prototype. Re-upload, same URL, instant update.
- The team reviews real interaction and motion, not a static frame.
- No version-name soup, no re-sharing the file on every change.
What It Did to the Loop on CRPKO
We use this building the CRPKO exchange. A trading terminal is mostly motion and state: the order book updating, a fill landing, liquidation, leverage changing the numbers. A screenshot cannot carry that. A live prototype can.
So the loop got shorter. I prototype in HTML, drop the link in the team channel, and feedback comes on the interaction itself. When I fix something, nobody re-downloads anything. They refresh the same link.
As a lead this is the cheapest process win I have made. Most of the cost in design feedback is not the thinking, it is the mechanics of getting everyone looking at the current version. The constant link removes that cost, and the team spends its attention on the design instead.
- CRPKO's terminal is motion and state. Static mocks lose it.
- Prototype, drop the link, feedback on the real interaction, fix, refresh.
- The win is removing the mechanics of sharing, not the thinking.