Back to collectionA 37-Second Test Reveals Two Kinds of Friction
The studio was trying to keep wallet steps from stopping new players at the game’s entrance. In one internal test, the full path from registration to entering the game took 37 seconds. The timing gave the team one concrete internal experience; it could not mean every player would enter the game in 37 seconds.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
The studio was trying to keep wallet steps from stopping new players at the game’s entrance. The second phase of wallet abstraction had reached internal testing. A-Zhen cared less about the speed of a single button than about where someone might hesitate on the journey from registration into the game.
In one internal test, the full path from registration to entering the game took 37 seconds. The figure showed the team how short the path could be, but also prompted a disagreement: people familiar with wallets found the prompts excessive, while newcomers might not know when confirmation was required. A-Zhen proposed recording the two groups’ difficulties separately, then reviewing the wording and order of the screens.
The timing gave the team one concrete internal experience; it could not mean every player would enter the game in 37 seconds. The second phase therefore turned toward finding where people got stuck, rather than simply shortening the clock. A-Zhen still needed to see whether different users could understand the flow, with details left to refine before public use.