Virtual Reward Mining Flutter App

Project Name: Virtual Reward Points & Idle Mining AppTech Stack: Flutter (Frontend) + Firebase (Backend)Target Platform: Android (Release AAB)Timeline: 10 – 14 Days1. Project Overview & ScopeWe require a lightweight, high-performance Flutter mobile application with a Firebase backend. The core concept is an "Idle Simulated Mining / Reward App" where users claim virtual reward points every 4 hours, view AdMob ads, refer friends, and request payouts.Important Compliance Note: This is NOT a hardware-based crypto mining application. It is strictly a simulated virtual reward game designed to comply with Google Play Store and AdMob policies.2. UI & Design SpecificationsTheme: Dark theme by default (modern, sleek aesthetic).Header (Top): Custom Telugu branding logo centered at the top.Home Screen Center: Prominent circular countdown timer showing the 4-hour claim window and an interactive "Claim / Mine" action button.Bottom Navigation Bar: 4 tabs:Home: Mining timer, daily points status, and claim action.Wallet: Total points balance, INR conversion estimate, transaction/claim history, and payout request form (UPI ID / Paytm / Bank).Referral: Unique referral link/code, list of invited users, and earned referral points.Profile: User info, app version, language switcher, contact/support link, and logout.Localization: Dual-language support togglable from the profile or welcome screen.3. Core Functional RequirementsAuthentication: One-tap Google Sign-In via Firebase Authentication.4-Hour Claim Loop:User taps "Start/Claim" to receive base points.A 4-hour countdown triggers before the next claim is accessible.AdMob Integration:Rewarded Video Ads: Triggered when the user claims points or opts in for extra points.Interstitial Ads: Placed logically between screen transitions with reasonable frequency limits.Test ad IDs must be used throughout the development lifecycle.Referral Mechanism:Each account generates a unique referral code.Referral rewards are credited only after the referred user completes a minimum verification threshold (e.g., at least 3 successful claims).Wallet & Withdrawal:Minimum withdrawal threshold configuration (e.g., 50,000 points = ₹50).Submission form capturing payout details (UPI ID / Phone Number).Status updates for user visibility: Pending, Approved, or Rejected.4. Security & Anti-Fraud Architecture (Critical)To prevent AdMob policy violations, invalid traffic penalties, and bot abuse, the following backend and client-side rules are mandatory:Server-Side Validation:Timer countdowns and points calculations must rely exclusively on Firestore ServerTimestamp, never on the device's local clock.AdMob Server-Side Verification (SSV):Rewarded points must only credit to the user's balance upon receiving and verifying an SSV callback via Firebase Cloud Functions.Device Binding & Anti-Cloning:Enforce a strict one account per device policy using unique hardware identifiers (Android ID).Implement basic emulator detection to block automated bot environments (e.g., Bluestacks, Nox).Root & Tamper Detection:Prevent access from rooted devices or environments with active debuggers/cheat tools.Rate Limiting & VPN Blocks:Implement safeguards against automated rapid-fire API requests and active proxy/VPN sessions.5. Admin Management (Backend)Structured Firestore collections for users, claims, transactions, and withdrawals.Ability for the administrator to review withdrawal requests, view total points earned vs. ads watched, and toggle statuses between Approved and Rejected.Firebase Remote Config integration to dynamically adjust point values, timer durations, and ad frequency without pushing app updates.6. Deliverables & MilestonesMilestoneDeliverableTarget TimelineMilestone 1Flutter UI implementation (Dark Theme, Reginal/English, Nav Bar) + Firebase Google AuthDays 1 – 4Milestone 24-hr Server Timer + Wallet & Referral logic + Admin Firestore rulesDays 5 – 8Milestone 3AdMob integration (SSV for Rewarded Ads) + Anti-fraud & Emulator checksDays 9 – 11Milestone 4Complete end-to-end testing, bug fixes, signed release AAB file, and full Flutter/Firebase Source Code handoverDays 12 – 147. Terms of AcceptanceSource code must be clean, modular, and well-commented.The project will be signed off once the release AAB builds without warnings and runs verification tests on physical Android test hardware.Test AdMob units must be active and cleanly decoupled from the final production ad units.