Cricket Software

Junior Cricket Scorer

Cricket is one of those games that seems bent on writing its own statistics and story into weekends. The rules can be complicated and scoring tedious.

I have programmed and produced a mobile iOS sports scoring app for Apple devices. The app is designed for U11 and U13 grade matches, where there are limits on the number of balls per over, but it can be used for other limited overs formats up to 50 over matches.

Ref: Cricket Scorer

A mobile app for junior cricket scoring showing the main score entry screen.

Cricket match animator

Match results can be very abstract and not visual. Here’s an app that I’ve made to improve that a little.

It is a fun, browser-based app that uses the cricket reports produced by the above cricket scoring app (and some other cricket match results sources) to recreate the match as an animated cartoon.

This link will take you to a demonstration of the app, that can run in a browser: Animation app

A cricket animation for viewing in a browser, that uses cricket data from the mobile cricket scoring app.

Junior Cricket Bowling Sequences

My local club has a requirement in the competition rules for U13 players to bowl in a sequence that conforms to certain rules, like this:

In each week, the team must use a preferred ‘bowling order’ which changes week to week (prepared using a rotation spreadsheet). However, it is not so simple as having the players bowl in the order in the weekly list. The effect of sub-clauses (a) to (d) is to impose a constraint/optimisation problem with the goal of finding valid sequences of bowling, given the preferred bowling order for players each week.

Sub-clauses (a) and (b) are both complicated by the fact that in a 30 over match one player will also be wicket-keeper for the first 15 overs (and will not bowl), and the other wicket-keeper only has the first 15 overs to complete their bowling before taking over as wicket-keeper. Sub-clause (c) imposes further restrictions that prevent a simple rotation through the weekly team list.

There may be more than one sequence of bowling that is valid, for a given number of players, but it helps to have at least one solution to work from. Here is a summary of valid, or near-valid sequences that satisfy the constraints (it may not be fully possible).

To assist the coach, I have written a python program that will take a list of player names (in a .csv file), and then generate the bowling sequence and show the cumulative number of overs bowled by each bowler. A link to the code will be provided in due course.