Ozo Golf

A round of golf takes four hours, most of it out of reach of a usable connection, and the phone is being handled by someone whose hands are wet and who is not looking for a settings menu. That constraint decided almost every technical choice in this project.

The application writes locally first. Scores, penalties and corrections go into a local store the moment a player taps, and a queue pushes them up whenever the network reappears. A round completed entirely offline reconciles when the player reaches the clubhouse. Two players scoring the same group produce a conflict, so we made the last confirmed card win and kept a full history rather than pretending it never happened.

The course maps are the second half of the product. Each hole carries distances measured from where the player is standing, drawn over a simplified outline that stays readable in bright sun. We spent longer than expected on contrast, and tested it outdoors rather than on a desk.

Behind it sits a web back office where the club sets up competitions, adjusts handicaps, and closes a season. That part is unglamorous and it is what the club uses every day.

What we would do differently

We built the conflict handling after the first competition rather than before it, and spent a weekend reconstructing four cards by hand as a result. On the next project of this shape, the sync rules get written down before the first screen.