Crickcounter: cricket scorer

What happens when you open it

You tap the icon, and the app loads directly into a match setup screen. No splash screen, no login, no ads interrupting the first launch. The interface is clean but basic. A text field asks for the team names. Below that, buttons for adding players. You type in the names, one by one. The keyboard pops up, you enter a name, hit done, and the app adds it to the list. It is functional but not polished. The player creation process is where the first signs of trouble appear. The app can hang or glitch during this step, according to multiple user reports. You add a few players, and suddenly the screen freezes for a second. You tap again, and it catches up. It is not a dealbreaker, but it is noticeable. Once the players are in, you start the match. The scoring screen is simple: big buttons for runs, wickets, and extras. You tap a button, and the score updates instantly. The CRR and RRR calculations appear at the top, updating automatically after every ball. For a street cricket match, this works. You do not need a physical scorebook. You do not need to do mental math. The app does it for you.

The real test comes when someone hits a six. You tap the six button. The score increases by six. The batsman's individual stats update. The strike rate recalculates. It happens in real time. The app does not lag during scoring, only during player creation. That is a curious trade-off. The developers prioritized in-match performance over setup smoothness. For gully cricket, where matches are short and setups are quick, this might be acceptable. The undo button sits at the bottom, ready for when someone accidentally taps the wrong button. In a crowded street with people shouting, that happens often. You tap undo, and the last action reverses. It is a simple feature, but it is the difference between a usable app and a frustrating one.

How the undo button and resume feature work together

The undo button is not just a convenience; it is a safety net. In gully cricket, the scorer is often also a player. Distractions are constant. The ball comes your way, you look up, and your thumb hits the wrong button. Without an undo, that error would corrupt the entire scorebook. With it, you fix it in one tap. The resume incomplete matches feature extends this logic. Matches in street cricket rarely finish in one sitting. Someone has to leave, it starts raining, or the light fades. You close the app, and later you open it again. The match is still there. You do not have to re-enter the players or the score. You pick up exactly where you left off. This is not a feature that gets mentioned in reviews often, but for anyone who has ever had to restart a match from scratch because the app crashed or they closed it by accident, it is essential. The combination of undo and resume means that even if you make a mistake or have to stop, the match data is safe. It is a workflow that is not explicitly described on the Play Store, but it is the app's strongest practical advantage. You can score a match in segments, over hours or even days, without losing progress. For local tournaments that span multiple days, this is invaluable.

Real-world performance and bugs

Performance is generally smooth during active scoring. The buttons respond quickly. The stats update without delay. However, the app has a reputation for crashes and hangs. User reports indicate that the app crashes when accessing certain features like MVP or leaderboard. It also has issues with no-ball counting. These are not minor bugs. In cricket, a no-ball is a critical event. It adds an extra run and gives the batsman a free hit. If the app counts it incorrectly, the entire match statistics are wrong. That is a significant flaw for a scoring app. The app also lags when starting a match. You set up the players, tap start, and there is a delay. It is not a long delay, but it is enough to be annoying. The developer has acknowledged some of these issues through updates. The changelog for the latest version mentions a "Toss feature added", which suggests the developer is actively working on the app. But the bug reports persist. The app is free, and for free apps, some bugs are expected. But for a tool that is supposed to replace a physical scorebook, accuracy is paramount. A wrong no-ball count is worse than no app at all.

The app also includes cricket wallpapers and a simple cricket board game. These are extra features that seem out of place. They feel like filler. The core functionality is scoring, and the extras do not add value. They might even distract from the main purpose. The app is developed by OTG Solutions, run by Miraj Ali Shaikh. The developer is based in Thane, Maharashtra, India. The app is free, with no in-app purchases. It is supported by ads, but the ads are not intrusive, according to user reviews. The app requires Android 10.0 or later. It is a relatively small app, at 31.2 MB. For a free app, it offers a lot of functionality. The question is whether the bugs outweigh the benefits.

Technical detail: version history and storage

The app has been updated regularly. Versions range from 37.0 to 73.0.0. The changelog for the latest version only says "Toss feature added". There is no mention of bug fixes or performance improvements in the published changelog. This is a common pattern with smaller developers. They add features but do not always document the fixes. The app stores match history locally. It does not require an internet connection to function. This is a critical feature for street cricket, where network connectivity is often unreliable. The app does not sync data to the cloud. If you uninstall the app, you lose your match history. There is no backup option. The app also does not have a Test cricket setup with 4 innings, which a user requested. The app is designed for shorter formats like gully cricket and T20. The storage permission is not explicitly listed on the Play Store, but the app likely needs it to save match data. The app does not request excessive permissions. It is a straightforward tool that does one thing: score cricket matches. The developer's email is provided for bug reports, which is a good sign of accountability. The app is not perfect, but for its target audience—casual street cricketers in India—it serves a purpose.