Cricket Scorer

Opening the App and Starting a Match

The first screen asks for team names. Type them in. No registration required. No account creation. Just two team names and a list of players. The app saves everything locally. The interface is sparse, almost utilitarian. A green button starts the match. Tap it and the scoring screen appears. Ball-by-ball. Runs, wides, no-balls, wickets. The buttons are large, easy to tap in a hurry. The undo button sits at the bottom. Unlimited undo, the developer promises. Tap it once, twice, ten times. Each tap rolls back one ball. That is the core workflow. Simple. Fast. No internet needed.

The app is built for one-day and T20 matches. That is the stated scope. Set the number of overs. Set the number of wickets. Start scoring. The scoreboard updates in real time. Batting stats. Bowling stats. Fall of wickets. Partnerships. All the numbers a scorer needs. The app saves the match state automatically. Close the app, reopen it, and the match resumes from where it left off. That part works reliably. The Google Drive backup is there, buried in the settings. Tap it and the app claims to back up teams, matches, and statistics. But some users report that no file actually appears in Drive. The app shows an updated time, but the backup never materializes. That is a gap between promise and delivery.

When Unlimited Undo Meets the End of a Match

The undo button is a powerful tool during a match. Made a mistake? Tap undo. Entered the wrong run? Tap undo. The app rolls back the last ball and lets you correct it. This works seamlessly during the game. The problem appears after the match ends. Once the match is saved and archived, the undo option disappears. You cannot edit the scorecard. If a catch was attributed to the wrong fielder, or a bowler's name was misspelled, the error stays. The app offers no post-match editing. This is a structural limitation. The unlimited undo is unlimited only while the match is live. Archive it, and the data becomes static. Several reviewers have noted this gap. One user wrote that they would like to "edit a score card after the fact. For example if a catch was attributed to the wrong person." The developer has not addressed this in recent updates.

The crash issue compounds this. One user reported that "the app crashes when a team gets all out. It doesn't completely shut itself off but it keeps playing as if the innings isn't over." If the app crashes during the final wicket, the match state becomes ambiguous. The undo button might not help because the match is technically over. The user has to guess whether the innings ended or not. The app does not handle this edge case gracefully. The developer's response to crash reports has been to advise updating to the latest version, but the changelog only says "Important bug fixes" and "Improved stability and performance." No specifics. No details on what was fixed. Users are left to test and discover whether their particular crash was addressed.

Ads, Overs, and the PRO Upgrade

The free version of the app includes ads. They appear between overs. Some users describe them as "intrusive" with "long waits." The ads disrupt the scoring flow. A scorer in the middle of a match does not want to wait through a 30-second video between overs. The PRO version removes ads. It also allows changing the number of balls per over and the number of wickets per innings. These are basic features that should be in the free version, but they are locked behind a paywall. The PRO upgrade is described as "very low cost," but the exact price is not listed on the Play Store. The app uses Google Play's billing system for in-app purchases.

The app does not support Test matches. This is a recurring complaint. Test cricket has four innings, unlimited overs, and different rules for follow-ons and declarations. The app is built for limited-overs formats only. One reviewer wrote, "Best app. But suggest to add Test cricket setup with 4 innings and each day as different options like 15overs, 30 overs, 60 overs, 90 overs." The developer has not added this feature. The app's description explicitly says it has features required for "one-day and T20 cricket matches." Test matches are outside the scope. But users keep asking for it. The absence of tournament management is another gap. No points tables. No leaderboards. No knockout stages. The app handles individual matches well, but it does not scale to leagues or tournaments. Competitor apps like CricScorer (by G12 Products) offer tournament modes with auto-scheduled fixtures and points tables. Cricket Scorer does not.

Permissions and What They Mean

The app requests a long list of permissions. INTERNET, ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE. These are for sharing scorecards and Google Drive backup. POST_NOTIFICATIONS is for alerts. WAKE_LOCK prevents the device from sleeping during scoring. BILLING is for in-app purchases. The Exodus privacy report lists seven trackers, including advertisement identification, profiling, and analytics. The app shares device or other IDs with third parties. Data is encrypted in transit, but it cannot be deleted. The developer's privacy policy states that app activity, app info and performance, and device or other IDs may be collected. This is typical for a free ad-supported app, but it is worth noting that the app collects more data than a simple scoring tool might need.