ScrollDate

Profile discovery uses the user's location, preferences, age range, interests, and radius to return nearby candidates while excluding blocked, banned, already-swiped, and already-matched users.

PostgreSQL/PostGIS handles geospatial filtering and distance ordering, keeping discovery rules close to the data.

Swipes use uniqueness rules so the same user pair is not processed repeatedly. Mutual likes create matches and conversations. Super likes follow premium-feature rules before they are accepted.

Chat uses authenticated Socket.IO connections. A user connects with a one-time token, the gateway verifies the session, registers the connection in Redis, and routes events to the recipient.

Messages are saved before realtime delivery. The REST API supports attachments, replies, read status, and unread counts. Participant checks make sure users can access only the conversations they belong to.

The message dispatcher uses Redis for active-session delivery and has Kafka/NATS publishing paths for downstream processing. That keeps message storage, delivery, and follow-up processing separated.

ScrollDate includes credits, Plus subscriptions, and paid features such as super likes and seeing who liked you.

The backend checks feature usage against plan limits, deducts credits when needed, and records credit transactions so paid actions can be audited.

RevenueCat webhooks process credit purchases and subscription lifecycle events. Events are marked as processed before balance or subscription updates are applied, which helps retries avoid duplicate credits or repeated subscription changes.

The admin console lets operators inspect profile details, block or unblock accounts, review posts, hide or restore content, and manage profile traits such as activities, feelings, personalities, and professions.

User and post tables support search, sorting, and product-specific filters such as plan, gender, preferred gender, age band, profession, profile completeness, photo presence, location presence, post visibility, and account state.

The admin API enforces role checks on the server. The Next.js admin app uses credentialed API requests, TanStack Query mutations, and confirmation dialogs for moderation actions.

ScrollDate's admin analytics help operators understand product activity without reading raw database tables. The dashboard includes overview KPIs and separate views for acquisition, retention, matching, monetization, and content.

Analytics filters cover plan, gender, preferred gender, age band, profession, profile completion, location/photo presence, subscription state, swipe action, super likes, transaction type, post privacy, and content state.

The frontend presents trend charts, KPI cards, and drill-down tables with Recharts and TanStack Query. The backend builds the aggregated data through typed Hono routes and PostgreSQL queries.

The mobile app talks to a Hono API running on Bun. Better Auth handles user sessions and admin access, Drizzle maps the PostgreSQL schema, and PostGIS supports location-based discovery.

AWS S3 stores uploaded media, Expo push notifications support interaction updates, RevenueCat handles in-app purchase events, and Redis stores realtime chat session state.

The admin console is a separate Next.js app. It connects to protected admin APIs for user management, post moderation, profile configuration, analytics, and monetization operations.