A cricket score tracking platform combining international match data with user-generated local cricket records.
- Quick Start
- Product Overview
- Problem & Solution
- Key Features
- Architecture & Design Decisions
- Access Control Model
- Prototype Details
- Risks & Metrics
- Roadmap
- About This Project
- Node.js (v14 or higher)
-
Clone the repository
git clone https://github.com/yourusername/crictrachpro.git cd crictrachpro -
Install dependencies
npm install
-
Set up environment variables
Create a.env.localfile in the project root:GEMINI_API_KEY=your_gemini_api_key_here
-
Run the development server
npm run dev
-
Open in browser
Visithttp://localhost:3000
CricTrackPro is a digital scorebook for amateur and local cricket. It lets players and organizers own, preserve, and showcase their personal cricket records—enabling weekend league players to move beyond scattered WhatsApp threads and notebooks.
- Not a replacement for professional cricket analytics platforms
- Not designed for ball-by-ball international predictive analysis
- Focused on grassroots-level record keeping and community
While international cricket data is everywhere, local and amateur cricket remains largely undocumented.
Players and organizers struggle with:
- ❌ No permanent ownership of local match records
- ❌ Loss of personal statistics over time
- ❌ Scattered scorekeeping across WhatsApp, notebooks, or spreadsheets
- ❌ Limited visibility of league or friendly matches beyond the ground
Existing cricket apps optimize for professional cricket, leaving a gap for grassroots-level record keeping.
Primary Personas:
- Amateur cricketers
- Weekend league organizers and players
Non-Goals:
- Deep analytical breakdowns of international cricket
- Replacement for professional scoring/broadcast systems
- Ball-by-ball predictive analytics (at this stage)
- Live and recent international match scores
- Data sourced from free, publicly available cricket APIs
- View-only experience for reliability
- Create local matches, leagues, or tournaments
- Add players and assign an admin role
- Admin-controlled scoring and match progression
- Automatic player profile linking
- Public visibility of local scorecards
When I open the app, I want to quickly view live international matches and live local matches created by users, so that I can stay updated while also tracking matches I personally play in or care about.
| Component | Behavior | Purpose |
|---|---|---|
| International Matches | Read-only | Reliability + clarity |
| User-Created Matches | Admin-editable | Ownership + control |
| User Type | International Matches | User-Created Matches |
|---|---|---|
| Any User | ✅ Read-only | ✅ View all |
| Match Admin | ✅ Read-only | ✅ Full edit + scoring |
| Non-Admin | ✅ Read-only | ✅ View only |
Design Philosophy:
- Admin-only editing reduces collaboration complexity
- Minimizes conflict resolution overhead in MVP
- Admin retains deliberate control over match closure
- ✅ Fully clickable user flows
- ✅ Mocked data (no backend persistence)
- ✅ Navigation & role clarity validated
- ✅ Match creation and viewing flows
- Navigation patterns
- Role clarity and permissions
- Match creation workflows
- User profile flows
The prototype focuses on product behavior and decision logic, not technical implementation. No engineering code is claimed.
- Google AI Studio – Prototype generation and interaction flows
- Node.js – Backend runtime
- Gemini API – AI-powered features
| Decision | Choice | Rationale |
|---|---|---|
| Speed vs Accuracy | Speed + mocked data | Faster iteration before building full scoring engine |
| Free APIs vs Reliability | Free APIs | Validate user demand before investing in paid sources |
| Collaboration Model | Admin-only editing | Reduce complexity; avoid multi-scorer conflict resolution |
- How will the system handle increased concurrent usage during live matches?
- How do we sustain engagement beyond match days?
- How do we prevent incorrect or malicious scoring by admins?
- How dependent are we on free external API reliability?
- Match Creation Rate – Local matches per daily active user
- Profile Completion Rate – User signup to profile completion ratio
- Engagement – DAU / MAU ratio
- Organizer Retention – Repeat match creation by same organizers
- Season-based leagues
- Points tables and standings
- Batting and bowling summaries
- Player comparisons against league averages
- Contextual insights inspired by international-level statistics
This project is part of my Product Management portfolio, created to demonstrate:
✅ End-to-end PRD thinking
✅ Clear scoping and tradeoffs
✅ Consumer + systems product judgement
✅ Comfort working with AI-assisted product tooling
Intent: Emphasize product clarity and decision-making over technical implementation.
This project is licensed under the MIT License – see the LICENSE file for details.
Feel free to open an issue or reach out for questions about the product strategy or implementation.
Happy tracking! 🏏