A fast global choice game, built as one product loop.

Make one choice feel consequential in seconds.

The core loop had to be understood without onboarding: see two options, commit to one, reveal the global split and move into the next decision. Every extra gesture or explanation weakened the game.

Product direction focused on pace, anticipation and the social value of the result. The interface gives the choice visual weight while keeping the aggregate answer as the payoff—not decoration.

Connect native interaction, result logic and production data.

The iOS client, production API and aggregate result contract were treated as one system. Loading, voting, repeated actions, unavailable content and sharing needed explicit states so the apparent simplicity survived real network behavior.

The result view communicates the global split without exposing individual voter data. Privacy boundaries were part of the product model, not a policy added after the interface was finished.

• Native iOS interaction
• Production question API
• Aggregate result logic
• Privacy-conscious sharing

Test the release paths that make the loop credible.

A focused release suite covered the important behavior and completed with 21 of 21 tests passing. The final presentation captures were produced from Release UI against production question and result data.

The evidence remains deliberately specific: passing tests, a live production API and completed store visuals. Those facts are stronger than a vague claim that the product is simply finished.

A small mechanic with a complete product surface.

TapWar emerged as more than a polished screen: a coherent game loop, native client, backend contract, sharing behavior, privacy boundary and launch presentation.

The broader lesson is useful for any consumer product. When the interaction is intentionally simple, the system behind it must be unusually disciplined—the user can feel every inconsistency.