PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu

ChillChat Clone - Features

ChillChat Clone Features: The Room Comes First

A social app can bolt audio onto a feed. The proposed platform starts from the room: drop-in voice with host, speaker and listener roles, hand-raise promotion and live presence, with streaming, gifting, missions and games built around it. Eighteen feature areas on twenty-eight entities, as recorded in the supplied specification; this preview does not implement or verify any of it. Here is what the specification covers, grouped by who touches it.

18 feature areas3 surfaces, one APIServer-side game state
28Entities behind 18 feature areas
190API route patterns
47XP level thresholds
71WebSocket events, in and out
01 / One session

What One Room Session Touches

The flow the supplied specification records for a single visit to a room.

01

Listener joins, presence broadcasts

02

Hand raised, promoted to speaker

03

Gift sent, coins leave the wallet

04

Diamonds land on the creator

05

XP awarded, mission progresses

06

Leaderboard and streak update

02 / By role

Feature Set by Role

Three surfaces run from one platform: a 42-route web app, a 46-screen Flutter build and an 18-section operator console, all against the same API - as recorded in the supplied specification.

01 - The Listener

Drops into live or scheduled rooms with a free-form topic, sees presence and mute state move in real time for everyone in the room, raises a hand to be promoted to speaker, and reads persisted chat. Private rooms are specified as enforcing their password on the server rather than by hiding the entry field, and capacity is configurable per room.

02 - The Host

Creates live or scheduled rooms, manages the three-tier role system across host, speaker and listener, promotes from the hand-raise queue and mutes per participant. The role model is proposed so a room stays manageable as it grows: microphone control, promotion from the hand-raise queue and per-participant mute all sit with the host.

03 - The Broadcaster

Goes live with server-side Agora RTC token generation, sees real-time viewer counts broadcast to all clients, and challenges another broadcaster to a PK battle with challenge, accept and live viewer voting. Active stream and active battle discovery feeds surface what is happening right now.

04 - The Creator

Receives gifts across ten tiers, from a one-coin heart to a five-thousand-coin castle. Coins are bought, diamonds are earned, and diamonds withdraw for real money at a configurable platform fee. That loop is the creator proposition, and it is why the gift tiers are modelled rather than being a single amount field.

05 - The Regular

Earns XP across forty-seven level thresholds, completes daily and weekly missions, keeps a streak, collects badges with rarity tiers and appears on leaderboards by week, month and room. Posts to a social feed across four content types with For You and Following tabs, stories, likes, comments, saves and shares.

06 - The Operator

Eighteen admin sections covering user and room management, the report and moderation queue, analytics with daily active users and retention cohorts, revenue with runtime platform-fee control, avatar and game catalogs, and broadcast notifications. Real-time text moderation is specified against five AI providers underneath.

Direct and group messaging with read receipts, an AI companion, video calls, avatar cosmetics and in-room games sit alongside these in the same eighteen areas.

03 / Compare

ChillChat vs This Build vs Building From Scratch

What each route gives you on the parts that decide whether a social audio app holds a community together. Pricing is deliberately not on this page - the cost shape lives on the development cost page.

What decides itThis build, as proposedBuilding from scratch
Time to a working appScoped in writingAn extended programme with a senior team
Room rolesHost, speaker and listener with hand-raise promotionAsk how roles and the microphone are managed past a dozen people
PresenceLive over Socket.IO, 71 events in and outAsk whether presence is live or polled
GiftingTen tiers, coins to diamonds to withdrawalAsk what the earnings path is behind the gift button
Retention47 XP thresholds, missions, streaks, badges, leaderboardsAsk whether the loyalty tooling can see your events
GamesSessions inside the room with server-side stateAsk where game state lives - a closed tab should not end the game
ModerationReal-time text moderation across five AI providersAsk whether moderation is real-time or after the fact
Source codeFull source across web, Flutter and admin in the proposed handover scopeYours, at the cost of building all of it

ChillChat itself is the reference for what this category looks like; it is not a product you can buy or self-host. The comparison that matters commercially is the second column against the third.

04 / End to end

How It Works, End to End

One member, traced from joining a room to withdrawing earnings, with every event and every balance change written down - as recorded in the supplied specification.

01

A room opens with a topic

Live and scheduled rooms carry a free-form topic, a capacity the host configures, and an optional password enforced on the server. Scheduled rooms sit in the same list as live ones, so a community can plan a session rather than only stumbling into whatever happens to be open.

02

Roles keep the room listenable

Host, speaker and listener are three distinct tiers rather than a permission flag. A listener raises a hand, the host promotes them, and per-participant mute is available throughout. Presence and mute state broadcast live over Socket.IO to everyone in the room, so the interface is designed to reflect the conversation rather than lag behind it.

03

Streaming adds a competitive hook

Any member can broadcast with an Agora RTC token generated server-side, with real-time viewer counts pushed to all clients. PK battles put two broadcasters head to head for viewer votes through a challenge, accept and live voting flow. PK battles are a proposed engagement hook: test whether head-to-head voting turns passive viewing into participation for your community.

04

Coins enter, diamonds come out

Coin packages are bought through Stripe on the web and RevenueCat-verified in-app purchase on mobile. A gift is sent from one of ten tiers, coins leave the sender's wallet, and diamonds land on the creator. The specification records coins converting to diamonds at one hundred to one and reversing at a ten percent fee, so the conversion path carries its own margin.

05

The action earns progress, not just points

The same gift awards XP against forty-seven level thresholds, advances daily and weekly missions, extends a streak, can unlock a badge with its own rarity tier, and moves the member on leaderboards scoped by week, month and room. The proposal ties the progression mechanics into the same event rather than beside it.

06

Games fill the room, not a separate tab

Trivia, charades and party games run as sessions inside an audio room with participant readiness, scoring and state held server-side. State is held on the server rather than in the client, so the game is designed not to depend on any one member's tab staying open.

07

The operator sees the same activity

Eighteen admin sections cover users and rooms, the report and moderation queue, analytics with daily active users and retention cohorts, revenue with a platform fee adjustable at runtime, the avatar and game catalogs, and broadcast notifications, with real-time text moderation specified against five AI providers underneath.

05 / Deliberate

Every Feature Earns Its Place

Each module below is in the proposed base scope for a reason, not because a competitor lists it.

ModuleWhy it is in the base build
Three-tier room rolesMicrophone control is a proposed requirement for rooms that grow: the hand-raise queue and per-participant mute are designed so a room can stay listenable as it fills.
Live presence over socketsIn an audio room the participant list is the product surface: presence is proposed as live so members can see who is actually in the room and who is speaking.
Server-enforced private roomsA password checked in the client is not a password. Private communities are an intended use case, so entry is enforced server-side.
Ten gift tiersA single tip amount cannot express the difference between acknowledgement and celebration - the tiers are designed so gifting can carry both.
Diamonds that withdrawThe earnings path is a proposed retention requirement: a platform where gifts stay as points gives creators no built-in reason to stay. Test whether withdrawal actually holds your creators.
47 XP thresholdsProgression depth is a proposed retention requirement: the specification records forty-seven thresholds so advancement does not run out early. Test whether the curve holds your members.
Server-side game stateSessions with readiness and scoring are proposed server-side, so the game does not depend on any one member's client staying open.
Real-time text moderationModeration is proposed as real-time text detection with a report queue behind it. Intervention still depends on operator response, and coverage is text only - media moderation is scoped separately.
Runtime platform-fee controlThe configurable fee is a proposed requirement because creator economics change as a community grows; evaluate how quickly the fee can be corrected on any platform you consider.

The AI companion, video calls, avatar cosmetics across five categories and four rarity tiers, and event tracking across twelve event types sit alongside these in the specification.

06 / Stack

The Technology Behind the Features

What the supplied specification records, and what that means for the team who inherits it.

Backend

Twenty-four NestJS modules exposing roughly 190 API route patterns from 248 controller methods, with twenty-eight entities behind eighteen feature areas.

Real time

Socket.IO carrying thirty-five inbound and thirty-six outbound event types, which is what makes presence, mute state, hand-raise promotion and live voting reflect the room rather than trail it.

Streaming

Agora RTC with server-side token generation for both audio rooms and video broadcasting, so the publish path is authenticated rather than open to anyone who reads the client.

Web

A 42-route web application carrying voice rooms, live streams, the social feed with stories, direct and group messaging, the wallet, missions and badges, the avatar shop and the AI companion.

Mobile

A 46-screen Flutter application against the same API, with RevenueCat-verified in-app purchase for coin packages so the mobile purchase path is validated rather than trusted.

Authentication

Email and password registration with verification, JWT access tokens with refresh token rotation, refresh tokens persisted per session and revocable, and a four-role model across user, VIP, moderator and admin.

A room list and a gift button are the easy part. The hard part is everything that has to stay in sync: presence and mute state for every participant, a hand-raise queue that promotes without a refresh, live PK voting that both broadcasters and every viewer see identically, and game sessions whose state survives a client disconnecting. Seventy-one socket event types is not a boast, it is the consequence of making a room feel live rather than merely look live. The stack is NestJS and Flutter on standard infrastructure, which matters when you hire against it and when a technical buyer runs due diligence on what you own.

07 / Honest readiness

What Is Not Included in the Base Package

Named here rather than discovered after scoping. These are proposed-scope boundaries from the supplied specification; none of them is implemented in this preview.

Agora capacity is yours to plan

Token generation and the join flow are in the proposed scope. What scales with your audience is the RTC minute plan and the region configuration, and on a platform designed to keep rooms open that is a recurring cost rather than a setup step.

AI moderation covers text, not media

Real-time text moderation is specified against five AI providers. Extending it to image and audio uploads at scale is the step once user-generated media volume justifies it, and it is scoped separately.

Audit logging is visible, not immutable

Operator actions are specified as visible in the console. Shipping an append-only audit trail to immutable storage for a compliance review is scoped as pre-launch hardening rather than something already in place.

Enterprise single sign-on is an integration

The role model is enum-based so operator roles are configuration, but connecting an enterprise identity provider is an integration step for a regulated deployment.

Payment rails are Stripe and RevenueCat

Both are in the proposed scope. A market-specific rail plugs into the same payment abstraction, and analytics streaming into a warehouse for business intelligence is a later step once a growth team needs it.

Every external provider runs on credentials you hold. A security and VAPT document can be shared before purchase rather than during a procurement review.

08 / FAQ

Frequently Asked Questions

Why do room roles matter so much?

The three-tier model of host, speaker and listener with hand-raise promotion and per-participant mute is a proposed requirement for rooms that grow: it puts microphone control with the host rather than leaving every microphone open. It is the difference the design draws between a group call and a venue, and it is why the room is the foundation rather than a feature.

Can creators actually withdraw what they earn?

As recorded in the supplied specification: coins are bought, gifts convert them into diamonds on the creator side, and diamonds withdraw for real money with an admin-configurable platform fee taken before payout. Coins convert to diamonds at one hundred to one and reverse at a ten percent fee. The earnings loop is modelled in full rather than approximated with a tip button, because a withdrawable path is a proposed retention requirement for creators.

What makes the games different from a mini-game tab?

They run as sessions inside an audio room, with participant readiness, scoring and state held server-side, so the game is designed not to depend on any one member's client staying open. Trivia, charades and party games are designed to be played by the room that is already talking rather than being a separate destination.

How is moderation handled in a live room?

Real-time text moderation is specified against five AI providers, with a report and moderation queue in the operator console behind it. Media moderation for image and audio uploads at scale is a scoped addition rather than part of the base build, and we name that rather than implying the coverage is total.

Is the mobile app at parity with the web app?

The specification records a 46-screen Flutter build against the same API, with RevenueCat-verified in-app purchase for coin packages, and the 42-route web app as the fuller surface. If mobile is your primary channel, ask us which flows are proposed on each surface before you commit.

Can I change the platform fee without a deployment?

The supplied specification records the platform fee on creator earnings as admin-configurable and adjustable at runtime. Creator economics change as a community grows, so evaluate how quickly the fee can be corrected on any platform you consider.

10 / Explore

Explore the ChillChat Clone

Five pages on this product. You are on Features.

Overview

The product page.

Back to overview

Development Cost

How pricing is scoped.

See the cost shape

Business Model

How the platform earns.

See the six lines

Development Company

What to check before you hire.

See the nine questions

11 / Next step

Walk through a room with us

Ask and we will trace a session with you: a listener joins, raises a hand, gets promoted to speaker, sends a gift, and the diamonds are followed through to the operator console. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead