We are looking for an experienced Android developer to build a professional Cricket Live Score Android application from scratch.
The app should have a clean, modern UI and be designed with scalability in mind so additional leagues and tournaments can be added easily in the future.
The project includes Android app development, backend development, admin panel, database, API integration, and deployment support.
Scope of Work
1. Live Score Integration
Integrate a Cricket Live Score API with support for:
Live Scores
Live Match Updates
Upcoming Matches
Completed Matches
Full Scorecard
Ball-by-ball Commentary (if available)
Match Info
Playing XI
Match Odds (if API supports)
Pitch Report
Venue Information
Toss Details
Match Results
Series & Tournaments
2. Manual Live Score Update
Sometimes third-party APIs delay score updates.
Need an admin feature that allows manual updates for selected matches.
Admin should be able to update:
Runs
Wickets
Overs
Current Batsmen
Current Bowler
Innings Status
Toss
Match Result
Commentary
Match Notes
Match Status
Manual updates should immediately override API data whenever required.
3. News Module
Need a complete news publishing system.
Features:
Create News
Edit News
Delete News
Featured Image
Categories
Rich Text Editor
Push Notification on Publish
The app should automatically display published news.
4. Admin Panel
Need a complete web-based admin panel.
Features:
Secure Login
Dashboard
Match Management
Manual Score Updates
News Management
Push Notifications
Advertisement Control
API Configuration
User Statistics
Match Visibility Controls
5. Website Backend & API Optimization (Very Important)
This project must not fetch live score data directly from the cricket API inside the Android app.
Instead, use the following architecture:
Cricket Live Score API
│
▼
Website Backend (Cache + Database)
│
▼
Android App
Requirements
Server fetches data from the Cricket API.
Store live data in the website database.
Android app fetches data only from our own backend.
Implement intelligent caching to reduce API usage.
Refresh intervals should be configurable (e.g., every 30–60 seconds depending on the match state).
Thousands of users should be able to use the app without increasing third-party API requests.
This requirement is essential to minimize API costs and improve scalability.
6. Advertisement Integration
Integrate Google AdMob.
Support:
Banner Ads
Native Ads
Interstitial Ads
App Open Ads
Rewarded Ads (Optional)
Ads should be easy to enable, disable, or update.
7. Push Notifications
Firebase Cloud Messaging integration.
Notifications for:
Match Starting
Toss Result
Wicket
Four
Six
Fifty
Century
Innings Break
Match Finished
Breaking News
8. Additional Features
Match Search
Favorite Teams
Share Match
Pull to Refresh
Offline Cache
Fast Loading
Material Design UI
Splash Screen
App Update Dialog
Privacy Policy
Contact Page
About Page
Settings
Dark Mode
Deliverables
Developer must provide:
Complete Android Source Code
Complete Backend Source Code
Admin Panel Source Code
Database Structure
API Documentation
Installation & Deployment Guide
Assistance with Play Store release
Bug fixes after delivery
Preferred Tech Stack
Android
Kotlin (preferred) or Java
MVVM Architecture
Retrofit
Room Database
Backend
Laravel (preferred) or Node.js
MySQL
Admin Panel
Laravel Blade or React
Notifications
Firebase Cloud Messaging
Important Technical Requirement
The solution should be built for high scalability and low API costs.
The backend should cache live score data and expose its own API to the Android application, ensuring that API requests remain low even with a large number of concurrent users.
Ideal Candidate
We're looking for someone who:
Has built cricket or sports applications before.
Has experience with real-time APIs.
Has Android and backend development expertise.
Understands API optimization and caching.
Can write clean, maintainable code.
Provides post-launch support.
When Applying, Please Include
Links to similar Android apps you've developed.
Experience working with cricket or sports APIs.
Your recommended tech stack.
Estimated development timeline.
Fixed-price quote.
Support period after project completion.
Suggestions to improve scalability, performance, and reduce third-party API usage.