StarShare

StarShare is built around one transaction: a fan picks a celebrity, fills in an occasion, a recipient name and relation, and instructions for the video, and pays. The order model (occasion, recipient, instruction, price, a user-submitted reference video/photo, the celebrity's delivered video, and an optional fan reaction video) carries that flow end to end, through pending/completed/cancelled/reported queues on both the fan and celebrity apps.

Payment runs through an integrated bank payment gateway with server-side payment confirmation.

The two audiences get deliberately different trust models. Fan accounts sign up with Google, Facebook or (on iOS) Apple, plus email, with a separate VIP invite-code flow; celebrity accounts are gated behind email/password plus phone-OTP verification and a submitted verification request an admin has to approve before the profile goes live — nobody can self-onboard as a celebrity.

Celebrities set their own per-video and per-message price, can opt to donate a percentage of proceeds to a named charity, and withdraw earnings to a bank account through a dedicated withdrawal flow with weekly/monthly totals charted in-app. The admin console runs a granular 14-permission RBAC system — separate view/update/create rights for celebrities, a distinct verify-celebrity-request permission, separate view vs. approve rights for withdrawals, separate view/update rights for users, plus orders, support, feedback and settings — so an admin account's dashboard changes based on exactly what it's been granted, not a blanket admin/non-admin flag.

Real-time Firestore-backed chat runs between fans and celebrities and, separately, between users and admin support. Fan-side discovery is Algolia-powered search plus Editor's Pick, Top Rated and New carousels, category browsing, and celebrity-profile deep links generated through Firebase Dynamic Links for sharing/referrals.