Why a golf scoring app has to work with no signal
Every course has dead spots, and the way an app handles them decides whether a group keeps scoring or reverts to paper. What correct offline behaviour looks like.
Updated 4 July 2026 · 5 min read · Flagstick team
Golf courses are the worst possible environment for a connected app. They are large, often rural, frequently wooded or below the surrounding terrain, and the one place a player stands still long enough to type is a green surrounded by trees.
Every course has dead spots. The question is not whether your scoring app will meet one, but what it does when it does.
What correct behaviour looks like
- The player taps a score.
- The app writes it to local storage on the phone immediately and shows it as entered.
- A background queue attempts to send it.
- If the send fails, it stays queued and retries.
- When signal returns, the queue drains and the shared leaderboard catches up.
- The player is never asked to do anything.
Step 6 is the whole design. Any behaviour that requires the player to notice a problem and respond to it will fail, because the player is playing golf.
Failure modes, in order of how badly they end
The app shows an error and discards the score. Worst case. The group loses trust immediately and someone gets a pencil out.
The app shows an error and asks the player to retry. Barely better. The retry happens on the same dead hole and fails again.
The app has an “offline mode” you enable in advance. Useless, because nobody knows where the dead spots are until they are standing in one. Offline must be the default behaviour, not a setting.
The app blocks the UI while sending. Every score entry takes several seconds on marginal signal, and the group stops entering scores because it is faster to remember them.
The app queues silently but never retries. Scores appear to be saved and never arrive. The player finds out at prizegiving. This is the one that destroys confidence for a whole season, because it is invisible while it is happening.
The thing that matters more than the queue
A retry queue is straightforward engineering. The harder part is what the leaderboard does with a group that is out of contact.
The board should show holes completed alongside the score. Then a group that has been offline since the 8th appears as “thru 8” rather than as a group scoring badly — and when their queue drains on the 15th tee, they jump seven holes at once, which is exactly right.
Without a “thru” column, an offline group looks like a collapsing group, and their playing partners get messages asking if they are all right.
What to ask a vendor
Ask this exact question, and listen for whether the answer is specific:
A group loses signal on the 12th tee and gets it back walking off the 17th green. What happens to the six holes in between?
A good answer describes local writes, a queue, automatic retry, and a leaderboard that catches up when the queue drains. It probably also mentions what the group sees while offline.
A bad answer is “it should be fine” or “most courses have coverage these days”. Most courses do not, and “should” is doing a lot of work in that sentence.
Follow up with:
What does the player see while they are offline?
The right answer is: their scores, entered, exactly as normal. Not a warning banner, not a spinner, not a queue count. The design goal is that the player never learns there was a problem.
Test it yourself before you commit
Cheaper than any evaluation process:
- Put the phone in aeroplane mode.
- Enter four holes of scores for a group.
- Force-close the app.
- Reopen it, still in aeroplane mode. The scores must still be there. This is the step that catches apps holding the queue in memory.
- Turn signal back on and watch the leaderboard.
Any product that fails step 4 will lose scores in the real world, because phones close background apps when the battery gets low — which, at the end of a five-hour round with the screen on, is exactly when it happens.
Battery, while you are at it
Related and usually ignored. A scoring app that holds a persistent connection, polls aggressively, or keeps the screen awake will flatten a phone before the 15th. On a society day that means the group’s scorer goes dark late in the round, which is the worst possible time — and on a golf trip abroad, with roaming and unfamiliar courses, worse again.
Reasonable behaviour: entry is cheap, the leaderboard refreshes when you look at it rather than continuously, and nothing runs hard in the background.
Frequently asked questions
- Do golf scoring apps work without an internet connection?
- Good ones do. Scores should be written to the phone’s local storage the moment they are entered and queued for upload, syncing automatically when signal returns. Apps that require a live connection to record a hole will fail somewhere on most courses, and a group that loses scores once usually goes back to paper for the rest of the season.
- What happens to a live leaderboard when a group has no signal?
- The group’s scores stop updating until their connection returns, at which point everything they entered appears at once. A well-designed leaderboard shows how many holes each player has completed, so an offline group reads as “thru 8” rather than as a group that has stopped scoring.
- How do I test whether a golf app works offline?
- Put the phone in aeroplane mode, enter several holes, force-close the app, and reopen it while still offline. The scores must still be there. Then restore signal and confirm the leaderboard catches up on its own. Apps that hold queued scores only in memory pass the first part and fail after a force-close, which is what happens in real life when a phone runs low on battery.
- Does live golf scoring drain phone battery?
- It can, if the app holds a persistent connection, polls constantly, or keeps the screen awake. Over a five-hour round that matters, because the group’s scorer going dark on the 15th is the worst possible failure. Look for an app where entering a score is cheap and the leaderboard refreshes when you open it rather than continuously.