Snooker Scores App - User Requirements and Navigation Map

User Requirements

The sort of person that would use the app is heavily into sport due to the obscurity of the snooker as a sport, so in that respect the person using the app is:

• A season ticket holder at a local football/rugby club.
• Potentially plays some sort of sport in an organised league.
• Gambles reasonably small amounts of money on major sporting events.
• Talks about sport within their social group.
• Likely to be male.

Because of this the app needs to be:

• Quick to access basic scores so it can be done while watching other sports without taking out too much viewing time.
• Allow the user to set notifications easily
• Using correct terminology so as not to patronise the user and increase the authenticity of the experience.
• Provide in-depth statistics about the games so users can track results for specific bets or have a point of discussion when talking about games.

It needs to avoid:

• Numerous steps of navigation.
• The monotonous standardised text-based display of results.

Navigation Map

In order to keep the navigation simple, the app will display live scores on the opening screen, put options to search for results via filtering a player or a tournament will be made clear. These search options will both need two screens, one for showing the options on each filter, and one for displaying the results from each search.

Any result or live score can be clicked on to get in-depth statistics of the particular game, which will be dictated by the sort of statistics that the commentators talk about and betting sites allow people to bet on. These are:

• Pot Success
• Long Pot Success
• Safety Success
• Balls Potted
• Highest Break
• Highest Break Breakdown
• Current Break
• Current Break Breakdown
• Session Breakdown

The detailed score screen will be the hardest to design because of all the information that will be required on it, with this in mind I'll need to develop a grid that suits this screen in particular.