Fan to Celebrity Gift web app project

Developer Requirements — Fan-to-Celebrity Gift Web App (Version 1) 1. Project Goal Build a fully functional, production-ready Web App, not a demo/prototype. The platform will allow fans to send/request physical gifts to celebrities, actors, influencers and creators while protecting their private addresses. Version 1 will use one central collection/processing station in Delhi, existing courier/postal services, and no own courier fleet. Android/iOS apps are not included in V1, but the architecture must support a future Android app using the same backend/API/database. 2. User Roles 1. Fan 2. Celebrity / Influencer / Creator 3. Admin Each role requires secure login, dashboard and role-based permissions. 3. Fan Features - Account creation and mandatory identity verification - Celebrity/creator search and public profiles - Request/invite non-joined celebrities - Submit gift requests - Unique Gift ID and QR code - Gift category/details - Declare food, fragile, letter/note, etc. - Gift tracking and notifications - Accepted / Not Accepted / Returned status - Anonymous identity visibility where applicable Basic functionality should be equally available to users. 4. Celebrity/Influencer Features - Account/login and mandatory identity verification - Profile management - Request/threshold notifications - View appropriate fan/request/gift information - Accept / Not Accept / Return handling - Gift status and notifications Private address and verification information must never be public. No public rejection leaderboard/count. 5. Non-Joined Celebrity Request & Threshold System Maintain separately: - Unique fans requesting a celebrity - Total requests/activity A fan must not create unlimited unique requests for the same non-joined celebrity. Suggested configurable thresholds: - Below 100 unique fans: no public indicator - 100+ unique fans: public interest/threshold indicator - Around 150: stronger invitation/outreach notification Admin should be able to configure thresholds. 6. Gift & QR System Each gift receives a unique Gift ID (e.g., GFT-000184) and linked QR code. Categories may include Clothing, Books, Letter/Note, Handmade, Food, Fragile and Other permitted items. Fan declares category, description, food/non-food, fragile/non-fragile, letter/note and handling information. 7. Physical Gift Workflow Fan → Station: Fan uses existing courier/postal service. Station: Staff scans/enters Gift ID/QR, verifies celebrity mapping, checks external package condition and declared handling information, identifies damaged/suspicious parcels according to SOP, updates status and stores/processes appropriately. Staff should not routinely open sealed parcels or unnecessarily read personal letters. Intact original packaging should not automatically be repacked. Extra outer protection should only be added when necessary. Station → Celebrity/Management: Existing courier/postal service. Suggested status flow: Received at Station → Processing → Dispatched → Delivered → Accepted / Not Accepted / Returned / Other. 8. Food Gifts Capture food declaration, received date/time, expiry/use-by where available and urgent handling requirement. Food gifts should trigger faster processing/notification. 9. Courier Charges Support displaying/calculating: 1. Fan → Station 2. Station → Celebrity/Management Courier API integration is not mandatory in V1. Developer should recommend the simplest reliable implementation. 10. Identity Verification — IMPORTANT Mandatory for every Fan and Celebrity/Influencer. Required capabilities where supported: - Government ID verification - Live document capture - Document quality checks - OCR/verification - Face verification/matching - Liveness - Automatic verification - Manual Admin review - Failure/resubmission Possible IDs: Aadhaar, Driving Licence, PAN, Passport, Voter ID and other Admin-approved IDs. Verification information must never be public. Developer must specify whether the solution is third-party, in-house or hybrid, including provider options, supported documents, API/per-verification cost, storage/security, automatic/manual process, failure/resubmission, retention/deletion and privacy limitations. 11. Admin Dashboard Admin must manage users, celebrities, requests, unique-fan counts, gifts, statuses, verification/manual reviews, thresholds, notifications, categories, document types, attempt limits, retention settings, suspicious activity and basic reports. Advanced analytics are not required in V1. 12. Notifications Support relevant notifications for: - Requests - Verification submitted/success/failed/resubmission/manual review - Gift received/processing/dispatched/delivered - Accepted/Not Accepted/Returned - Threshold reached Developer should recommend the most cost-effective V1 notification method. 13. Security & Privacy Production-level basic security is required: HTTPS/SSL, secure authentication, password hashing, role-based access, admin protection, input validation, rate limiting, spam protection, secure database, audit logs, backups, secure/encrypted verification-document storage, access logging, retention/deletion policy and suspicious-activity monitoring. Security/privacy must not be compromised merely to reduce cost. 14. NOT Required in V1 - Android/iOS apps - AI chatbot/live chat - Advanced AI - Advanced analytics - Multiple warehouses - Own courier fleet - Complex courier API integrations - Complicated premium subscription - Unnecessary third-party integrations 15. Future Android & Ownership Backend/API/database/authentication/business logic must be structured so a future Android app can use the same system without rebuilding the backend. After completion, I must receive: - Complete source code - Git repository - Backend/API and database structure - Development/deployment configuration - Domain/hosting access - Admin credentials - API/configuration documentation - Backups - Verification integration documentation Important project accounts must remain under my/company control. Infor