Many grounds have weak data, so County Cricket never asks the network for permission before it records a ball. Whatever you tap is written to storage on your phone first. Sending it to the server is a separate step that happens in the background.
What happens to a ball
- You tap. The engine updates the score and the ball is saved on the phone.
- The change joins a queue of things to send.
- When the phone has a connection, the queue is sent in order, one after another. If a send fails, the app tries again on its own when the network or the app comes back.
- The server accepts the newest state, and the website and other phones update.
You never press “sync”. While the phone is offline or still catching up, a banner shows Offline with the number queued — for example Offline · 12 queued — and offers a retry once you are back online.
One phone scores at a time
A match has a single scoring seat. If you hand scoring to another phone from Match settings, the old phone turns view-only, so two phones can never both change the score. The server also rejects a stale update from an older phone, so a phone that was replaced cannot overwrite the new scorer’s balls.
What watchers see
The website and the app show the last state that reached the server. If nothing arrives for about 45 seconds during a live match, the website shows that the scorer looks offline. That is not an error: the missing balls appear in order once the scorer reconnects.
Good habits
- Set up the match and any Match Crew invites while you still have data — looking up a player’s number and sending an invite need the network.
- Keep the app installed and do not clear its data until the last balls have synced.
- After the final ball, come online once (Wi-Fi at home is fine) so the result reaches the website.
- Go Live needs a network the whole time. Scoring does not.
