About Gully Crix

It started with a fight

Gully Crix didn't begin with a business plan. It began with a brawl.

One regular Sunday gully match, last over, scores close — and then the argument everyone who has ever played knows too well. “That was 87.” “No, it was 91.” Nobody had written anything down. A shove became a shout, the shout became a scuffle, and a game that was supposed to be the best part of the week ended with friends not talking to each other. Over a number nobody could prove.

I went home annoyed and did the obvious thing: looked for an app to keep score next time. What I found made me more annoyed than the fight had.

So I built the thing I couldn't find

Every cricket app I tried was built for professional 11-a-side cricket — full squads, player registration, logins, internet, forms before you could record a single ball. None of them understood gully cricket: six players a side, made-up team names, no wicket limit, patchy mobile data, and a scorer who is also fielding.

So I built Gully Crix myself, solo. The brief was simple: start a match in under ten seconds, work fully offline, need no account, and never get in the way. One tap per ball. Undo when the scorer fumbles. A clean scorecard to drop in the group chat when it's done. That's it.

Everything since — the built-in coin toss, live match streaming, Super Over and Bowl Out tiebreakers, published match pages — has been added the same way: because players asked for it, not because a roadmap said so.

This isn't only about arguments. It's about safety.

Here's the part I didn't expect to be writing. The longer I worked on this, the clearer it became that a disputed score isn't always a harmless squabble. In India and across South Asia, it is not hard to find news reports of cricket disagreements — many of them over scoring, run-outs, or who really won — escalating into serious violence. People have been badly hurt. In the worst cases, people have died. Over a local game.

That sounds extreme until you've stood in the middle of one of these arguments. Tempers, money on the line, a crowd watching, and no neutral record of what actually happened — that's the whole problem in one sentence. When nobody can prove the score, the loudest and the angriest win.

A reliable, ball-by-ball scorecard takes that fuel away. When every delivery is recorded as it happens and anyone can pull up the breakdown, the factual dispute simply disappears — and so does the spark that lights most of these fights. It would be a stretch to put it any grander, but keeping the score indisputable genuinely keeps games friendlier and, in more cases than I'd have guessed, keeps people safe. That's a big part of why this app exists.

It's in the news more often than it should be

These are real, reported incidents — credit to the original outlets. They're extreme outcomes, but they all start the same way: a score nobody can prove. Know a report we should add here? Send it to us.

Where Gully Crix is today

What started as one annoyed player's side project is now used by thousands of players across India and beyond.

Who's behind it

Gully Crix is built and maintained by Abhishek — a developer and lifelong gully cricketer — under Codesign FZ-LLC. It's an independent, self-funded project, which means there's no investor pushing for ads or paywalls, and feedback from real players shapes what gets built next.

If you've got an idea, a bug, or a story about a match that nearly ended in a fight — get in touch or join the WhatsApp community from the home page. I read every message.

Score your next match properly

Free, offline, no login. Settle the score before it ever becomes an argument.