What we're building next
The next part of The Shot is the path from one phone joining to a whole arena playing together.
We're building it from the network up: what reaches the phone, how it joins, how phones connect and coordinate, what happens during a turn, and what the system records along the way.
As each piece is built, we'll add what we learn here.
Start with the connection
How much does the phone have to pull down?
We're building the join so the phone gets only what it needs to enter the game. We'll measure the actual download as that path takes shape.
How long from scanning to playing?
The path starts at the QR code and ends when the player is in the game. We'll measure the full trip, not just page load.
What happens when a whole stadium joins in the same minute?
The same join has to work across an arena, whether people arrive through venue Wi-Fi or their own connection. That's the scale we're building toward.
How do phones talk to each other outside one Wi-Fi?
We're using Iroh so a phone carries an identity of its own rather than depending on whatever network address the room gives it. The next step is putting The Shot on top of that at arena scale.
Who coordinates each sector?
One phone doesn't direct twenty thousand. We're building coordinating roles that can live on a desktop or in the cloud, then we'll determine how many the arena actually needs.
What happens if the network changes halfway through a turn?
The game and the architecture meet here. We're defining what a turn does with the actions that arrived, and how play continues when connectivity changes.
One code for everyone, or one per entrance?
We're building the join flow so we can decide where a player's sector identity should be assigned: before they arrive, or as they connect.
Then the game
How long is a turn?
Forty seconds is the current design. As the delivery path is built, we'll be able to set the turn length from what the system actually does.
How are roles dealt?
Roles can be assigned randomly or by proportion. Either way, we're building the organizer as the source of that assignment, so every role can be accounted for.
Who takes the Final Shot?
That's a game-engine decision, not a screen decision. The rule will live with the rest of the game state.
And measure it from day one
What gets counted at the end?
Participants, actions, connections and the path through a game. We're adding the instrumentation as we build, so those numbers exist when there's a real arena run to measure.