Cricket Club Payments App Development

₹1500-12500 INR

Posted 1 minute ago

•

Ends in 6 days

₹1500-12500 INR

Paid on delivery

Android app for cricket clubs: match-fee payments, WhatsApp reminders and subscriptions SUMMARY Build an Android app (iOS in phase 2) that helps amateur cricket club captains collect weekend match fees, chase late payers on WhatsApp with funny reminders, take payments online, and reconcile every rupee at month-end. It will be sold to many clubs on a monthly subscription. Later, partner sports shops will sell products to players inside the app. A working prototype defines the exact screens, behaviour and design. Open it on a phone: [login to view URL] THE PROBLEM A club plays about 8 matches a month. A captain pays the ground Rs 8,000 to 11,000 per match and splits it across 11 to 12 players (about Rs 800 each). Captains rotate weekly, payments are tracked by hand in WhatsApp, and at month-end nobody knows who still owes what. USERS AND ROLES - Club owner (admin): logs in with phone OTP, can do everything on every match, removes captains, manages the subscription. - Captain: invited by the owner. Creates their own matches, marks payments only on their own matches, edits their profile (name, UPI ID, bank details), adds players, sends reminders, sees all reports. - Player: no login. Only receives WhatsApp messages and pay links. - All permissions must be enforced on the server, not only hidden in the UI. SCREENS (bottom tab bar: Home, Matches, Nudge, Month-end, Squad) 1. Home: greeting, a hero card with the amount left to collect, collected, players pending and next deadline. Quick actions. Top 5 players who owe, each with a Nudge button. Next match. Month-end shortcut. 2. Matches: All / My matches toggle. Match card shows date, ground, captain, collected of expected, progress bar, per-head and a deadline tag. Player chips: tap to mark paid or unpaid (green paid, red overdue, grey pending), disabled for other captains' matches. Buttons: Fixture post, Group nudge, Roll call, Edit, Delete. 3. New / Edit match: date (defaults to next Saturday), ground, opponent, ground fee, per-head (auto, can override), squad picked from saved players plus guest names, and a live calculation like "11 players x Rs 800 = Rs 8,800". 4. Nudge: tone selector (Auto, Gentle, Midweek, Thursday, Overdue, Roast). One card per player who owes, combining all their unpaid matches, with message preview and buttons Send on WhatsApp, Copy, New joke, Mark paid. A Hall of Shame button posts a group roast of overdue players only. 5. Month-end: month switcher. Shows ground fees (X), received (Y) and short (X - Y). Report 1 by match: what each match is short and who has not paid. Report 2 by player: who owes, for which dates and captains. By-captain summary of ground paid vs got back. Share on WhatsApp, Copy, Download Excel (CSV). 6. Squad: captains (name, UPI ID) and players (name, WhatsApp number, amount owed). Add, edit, remove. BUSINESS RULES - Per head = round up (ground fee / squad size) to the nearest 10. Example: 9,000 / 11 = 820. - Payment deadline = the Thursday on or before the match date. - Overdue = unpaid after the deadline. A match is settled when everyone has paid and the date has passed. - A player's dues = per-head of every match where they are unpaid, across all captains. - Auto tone uses the player's earliest deadline: 3+ days away = Gentle, 1 to 2 days = Midweek, same day = Thursday, any overdue = Overdue. Roast is chosen manually. - Month-end: X = sum of ground fees; Y = sum of per-head of paid entries; Short = X - Y (minimum 0). Also show unpaid amount, rounding surplus and fees. - Two-tap confirmation for delete, remove, mark all paid. No pop-up alerts. WHATSAPP MESSAGES The app opens WhatsApp with text pre-filled ([login to view URL] links to the player's number, or to any chat for group posts). Messages are friendly Hinglish with emoji. Types: fixture post (date, ground, per-head, pay details, deadline, numbered squad), player nudge (a tone line, each unpaid match, one pay link for the total), group nudge (count paid, no names), roll call (paid and pending names), Hall of Shame (overdue players ranked, one funny line each), month-end summary. Sample lines: - Gentle: "Bhai, net practice baad mein, pehle UPI practice. Bas Rs 800." - Thursday: "Yaar, aaj Thursday hai. Abhi toh payment kar de, warna Saturday ko 12th man + drinks duty pakki." - Roast: "Tera strike rate aur payment rate dono same hain: zero." Keep all message lines in a config file. The full message bank is shared after hiring. PAYMENTS (Razorpay, or Cashfree if you argue for it) 1. Match fees (phase 1): each player gets a personal pay link (UPI, cards) for exactly what they owe, covering one or more matches. A Razorpay webhook (signature verified, safe against repeats) marks those matches paid automatically and notifies the captain. Money settles to the captain's bank account through Razorpay Route linked accounts, or to one club account if the club prefers. Configurable platform fee per club, optional convenience fee to the player, refunds by the captain or owner. Manual marking stays for cash, labelled Online or Manual. Month-end shows online vs manual totals and fees. 2. Club subscription (phase 1): free 30-day trial, then a monthly plan per club. Use Google Play Billing inside the Android app (digital service), Razorpay Subscriptions for web sign-ups. When it lapses, new matches are locked but reports stay readable. 3. Sports-shop marketplace (phase 2): shop onboarding with GST and bank details, shop dashboard for products and orders, player Shop tab with catalogue, cart, checkout, pickup or delivery, platform commission per order with automatic split and settlement. Phase 1 must be designed so this adds screens, not a rebuild. DATA (Firestore suggested, SQL acceptable) users, clubs (plan, trial, subscription status, fee rules), clubs/members (role, UPI, linked account, KYC status), clubs/players, clubs/matches (date, ground, captain, fee, per-head, squad with paid flag, source, payment id), clubs/invites, payments ledger (type, items, amount, gateway fee, platform fee, status, transfer and refund ids), and for phase 2 shops, products, orders. Keep an audit trail of who marked each payment. DESIGN Dark, premium fintech style (CRED-inspired, our own branding). Background #0A0A0B, cards #131315, text #F3F2EE, paid green #7FE3AB, due coral #FF8370, accent gold #D9C49A, WhatsApp buttons #25D366. Fonts: Outfit and Manrope. Pill buttons, bottom sheets for forms, a black hero card with a red cricket ball. Must match the prototype and work from 360 px wide screens. TECH Flutter or React Native, Firebase (phone OTP auth, Firestore with security rules, Cloud Functions for webhooks and scheduled jobs, FCM push), Razorpay (Payment Links, Route, Subscriptions), Google Play Billing, Crashlytics. Real-time sync between captains. Offline viewing. Push reminders on Monday (post fixture), Wednesday and Thursday (dues pending) and month-end. Web admin panel for clubs, subscriptions, payments, refunds and disputes. Privacy policy, terms, account deletion, Play Store Data safety form. MILESTONES (about 7 weeks for phase 1) 1. Week 1: setup, OTP login, create club, invite captains, squad. 2. Week 2: matches, per-head maths, marking payments, real-time sync, server permissions. 3. Week 3: WhatsApp messages and tones, Hall of Shame, month-end reports, CSV, push reminders. 4. Week 4: pay links, webhooks, captain bank onboarding, Route settlement, refunds, platform fee. 5. Week 5: subscriptions, admin panel, design polish, start 14-day Play closed test. 6. Weeks 6 to 7: fixes, live payment testing, store listing, release. Phase 2 (separate quote): iOS app and the sports-shop marketplace. ACCEPTANCE CHECKS - One captain marks a payment; another captain's phone shows it within 5 seconds. - A captain cannot change another captain's match, even via the API. - 9,000 with 11 players gives 820 per head; a Sunday match is due the Thursday before. - Month-end short equals ground fees minus received for a month of 8 matches. - A pay link covering 2 matches marks both paid automatically within 10 seconds. - Settlement reaches the right captain minus fees; a refund reverses it; fake or repeated webhooks change nothing. - Two clubs never see each other's data. Works on Android 10 and above. DELIVERABLES Full source code in my GitHub, Firebase and Razorpay accounts in my name, signed release (AAB) and keys, store listing assets, README for build and deploy, and 30 days of bug fixes after launch. IN YOUR BID Play Store links to apps you have shipped (especially with payments), your stack choice, fixed price per milestone, and your timeline.

Project ID: 40830480

About the project

4 proposals

Open for bidding

Remote project

Active 20 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

用 HomepageTab 新标签页关注 RSS,打开浏览器就能看到更新。

安装 HomepageTab