System Requirements Document for del

1. Introduction

DEL is an Android voice-room social app built for a loud, glossy, nightlife-flavoured live-audio economy. The product intent, taken directly from the authoritative requirement thread, is to deliver an APK named DEL that hosts many live voice rooms where users talk, listen, send premium gifts (frames and vehicles) priced expensively, pay per chat message and per video call, play a lucky draw / jackpot (JP) feature, claim ampou bonus rewards, and hold a diamond and coin balance — including an unlimited diamond and coin balance for the owner's account — with the ability to sell and transfer coins to other users.

The audience is young Southeast-Asian mobile users who want volume, shine and status: hosts who run rooms, listeners who join and spend, and coin/diamond traders who move value and buy expensive gifts. The emotional register is nightlife — loud, glossy, lucky, immediate.

This document is the single source of truth for the current delivery. It preserves every explicit capability, constraint and named value from the requirement thread, and marks inferred mechanics honestly.

2. System Overview

DEL is a mobile-first Android application (delivered as an APK) backed by a first-party service that owns durable accounts, rooms, balances, charges, gifts, transfers, jackpot activity and bonus claims. The current delivery includes:

• Many live voice rooms that hosts create and operate, and that listeners browse and enter.
• Premium gifts — glossy frames and vehicles — priced expensively, sent inside rooms.
• Paid chat charged per message and paid video calls charged per call.
• A lucky draw / jackpot (JP) feature.
• Ampou bonus rewards that users claim.
• A diamond and coin wallet, including the owner's unlimited balance.
• Coin selling and transfer to another selected user.

Actors are the closed accepted persona set: Room Host, Room Participant / Listener, and Coin/Diamond Trader. The backend is a non-persona system actor; there are no external provider surfaces in the current scope.

2a. Product Interpretation and Delivery Boundary

DEL is delivered as a first-party Android APK with application-owned identity. Because balances, rooms, gifts, charges, transfers and jackpot activity are durable and must remain bound to the correct participant, the app owns account creation and returning-user verification. Anonymous visitors can read the public entry surface; every protected destination (rooms, gifts, chat, calls, transfers, lucky draw, bonus, wallet) requires an established identity.

The current horizon covers the capabilities listed above. Anything not stated in the authoritative thread — for example, real-money cash-out rails, external payment processors, or third-party social integrations — is out of current scope and is not implemented as product behaviour. The gambling-adjacent bonus loop, unlimited owner balance, and coin resale are treated as in-app virtual-currency mechanics owned entirely by DEL; no external financial settlement is introduced.

2b. Source Content Inventory

Not applicable — no reference directive in this request declares content_source.

2c. Page Content and Component Coverage

The page inventory below is the closed, ordered page contract for this generation. Each page appears exactly once.

Landing

• Information / state: Anonymous public entry. DEL wordmark as a glossy 3D pink capsule-sculpture; oversized live counter ("12,480 rooms live") with the number in gold and the words in near-white; a horizontally drifting row of live room capsules (host avatar ring, room name, listener count).
• Primary actions: "Masuk Room" fat pink capsule (routes to Login when no identity is established, otherwise to Voice Rooms); "Lucky JP" gold capsule (routes to Login when no identity is established, otherwise to Lucky Draw).
• Supporting actions: Open Login; open Sign Up.
• Domain entities: Live room summary (name, host, listener count), live-room count.
• Component responsibilities: Hero wordmark sculpture; live counter; draggable/auto-drifting room capsule row; bottom-left CTA cluster; lime rim-light arc.
• States: Loading — capsule row skeleton with pulsing pink live dots. Empty — "Belum ada room live" with a Sign Up capsule. Success — populated capsule row and live counter. Error — "Gagal memuat room" with a retry capsule. Recovery — retry re-fetches the room list without leaving the page.

Login

• Information / state: Returning-user verification form (identifier + secret). Anonymous access.
• Primary actions: Submit credentials to establish identity.
• Supporting actions: Navigate to Sign Up; return to Landing.
• Domain entities: Account identity.
• Component responsibilities: Credential fields; submit capsule; inline validation messaging.
• States: Loading — submit capsule in progress. Empty — pristine form. Success — redirect to the destination the user was attempting to reach. Error — "Kredensial tidak valid" inline, form retained. Recovery — user may correct and resubmit, or switch to Sign Up.

Sign Up

• Information / state: Self-service enrollment form for a new durable account. Anonymous access.
• Primary actions: Create account and establish identity.
• Supporting actions: Navigate to Login; return to Landing.
• Domain entities: Account identity, initial wallet (diamond + coin).
• Component responsibilities: Enrollment fields; submit capsule; inline validation messaging.
• States: Loading — submit capsule in progress. Empty — pristine form. Success — identity established, redirect to the intended protected destination. Error — field-level validation or "Pendaftaran gagal" with the form retained. Recovery — correct and resubmit, or switch to Login.

Voice Rooms

• Information / state: Browsable list of live rooms as living pills — glossy avatar ring, pulsing pink live dot, ticking listener count. Role-restricted (established identity).
• Primary actions: Enter a room.
• Supporting actions: Navigate to Create Room; open Wallet ribbon.
• Domain entities: Live room (name, host, listener count, live status).
• Component responsibilities: Room capsule list; live-dot indicator; listener-count ticker; entry control.
• States: Loading — capsule skeletons. Empty — "Belum ada room" with a Create Room capsule. Success — populated list with ticking counts. Error — "Gagal memuat room" with retry. Recovery — retry re-fetches; user may instead open Create Room.

Create Room

• Information / state: Room setup and live-operation surface for the host. Role-restricted (Room Host).
• Primary actions: Create and open a live room; end the room.
• Supporting actions: Configure room name; view current listeners.
• Domain entities: Room (name, host, live status, listener roster).
• Component responsibilities: Room-name field; create capsule; live-status control; listener roster.
• States: Loading — create capsule in progress. Empty — no room yet, setup form shown. Success — room live, host sees listener roster. Error — "Gagal membuat room" with retry. Recovery — retry creation; if the room drops, host may re-open it.

Room Gifts

• Information / state: Gift-sending surface inside an active room. Login required. Shows the gift catalogue with expensive prices for frames and vehicles.
• Primary actions: Select a gift and send it to a chosen recipient in the room.
• Supporting actions: Preview gift artwork; view price.
• Domain entities: Gift (frame, vehicle), price, sender, recipient, room.
• Component responsibilities: Gift catalogue with glossy 3D props; price tags; recipient selector; send control; gift-send arc animation.
• States: Loading — catalogue skeletons. Empty — "Belum ada gift tersedia". Success — gift arcs to recipient, pink shockwave ring, gold price tag snaps in and fades. Error — "Saldo tidak cukup" or "Gift gagal terkirim" with the selection retained. Recovery — top up via Wallet or retry the send.

Gift Collection

• Information / state: The user's owned and equipped frames and vehicles. Role-restricted.
• Primary actions: Purchase a frame or vehicle; equip an owned frame or vehicle.
• Supporting actions: Browse the full catalogue; view owned items.
• Domain entities: Gift (frame, vehicle), ownership, equipped state, price.
• Component responsibilities: Owned-item grid; catalogue browser; purchase control; equip control.
• States: Loading — grid skeletons. Empty — "Koleksi kosong" with a browse-catalogue capsule. Success — item purchased and/or equipped, reflected on the avatar. Error — "Pembelian gagal" or "Saldo tidak cukup". Recovery — retry purchase or top up via Wallet.

Room Chat

• Information / state: Paid text chat inside an active room, charged per message. Role-restricted.
• Primary actions: Send a message (charged per message).
• Supporting actions: View message history; view per-message charge.
• Domain entities: Message, sender, room, per-message charge.
• Component responsibilities: Message list; composer; charge indicator; send control.
• States: Loading — message history skeletons. Empty — "Belum ada pesan". Success — message appears in the list and the charge is deducted. Error — "Saldo tidak cukup" or "Pesan gagal terkirim", draft retained. Recovery — top up via Wallet or resend.

Video Calls

• Information / state: Video-call surface, charged per call. Role-restricted.
• Primary actions: Start a video call; end a video call.
• Supporting actions: Select a call recipient; view per-call charge.
• Domain entities: Call session, participants, per-call charge.
• Component responsibilities: Recipient selector; call controls; charge indicator; call state display.
• States: Loading — connecting state. Empty — no active call, recipient selector shown. Success — call connected, charge applied. Error — "Saldo tidak cukup" or "Panggilan gagal tersambung". Recovery — top up via Wallet or retry the call.

Coin Transfer

• Information / state: Sell/transfer coins to another selected user. Role-restricted (Coin/Diamond Trader).
• Primary actions: Select a recipient user, enter an amount, and transfer coins.
• Supporting actions: View current coin balance; view transfer history.
• Domain entities: Coin balance, recipient user, transfer record.
• Component responsibilities: Recipient selector; amount field; transfer control; history list.
• States: Loading — history skeletons. Empty — no transfers yet. Success — coins move to the recipient and the transfer appears in history. Error — "Saldo tidak cukup" or "Transfer gagal". Recovery — correct the amount or recipient and retry.

Lucky Draw

• Information / state: The JP lucky draw as a glossy pink-and-gold liquid disc with a lime teardrop pointer. Role-restricted.
• Primary actions: Spin the JP wheel.
• Supporting actions: View spin cost; view recent JP results.
• Domain entities: Spin, prize segment, JP result, spin cost.
• Component responsibilities: Liquid disc wheel; teardrop pointer; spin control; result display.
• States: Loading — wheel initialising. Empty — no spins yet. Success — wheel spins with real deceleration, winning segment floods the screen with gold for 600ms, result settles. Error — "Saldo tidak cukup" or "Spin gagal". Recovery — top up via Wallet or retry the spin.

Bonus Rewards

• Information / state: Ampou bonus rewards available to claim. Role-restricted.
• Primary actions: Claim an available ampou bonus.
• Supporting actions: View claimed history; view claim eligibility.
• Domain entities: Bonus reward, claim state, claim history.
• Component responsibilities: Reward list; claim control; history list.
• States: Loading — reward skeletons. Empty — "Belum ada bonus tersedia". Success — bonus claimed and credited to the wallet. Error — "Bonus gagal diklaim" or "Bonus sudah diklaim". Recovery — retry the claim or return later.

Wallet

• Information / state: Diamond and coin balances as a display object — oversized Unbounded gold numerals on a glossy plum slab with a sliding specular highlight; digits roll individually on change. Login required. Shows the owner's unlimited balance state.
• Primary actions: View balances.
• Supporting actions: Navigate to Coin Transfer; navigate to Gift Collection; view balance history.
• Domain entities: Diamond balance, coin balance, unlimited-balance flag, balance history.
• Component responsibilities: Balance display slab; rolling-digit numerals; unlimited-balance indicator; navigation capsules.
• States: Loading — balance slab skeletons. Empty — zero balances shown truthfully. Success — balances render with rolling digits on change. Error — "Gagal memuat saldo" with retry. Recovery — retry re-fetches balances.

3. Functional Requirements

Each requirement is a distinct story point with provenance, lifecycle facts and observable acceptance.

FR-1 — Android APK delivery named DEL (explicit) As a user, I should install and open the DEL Android APK so that I can use the voice-room app.

• Trigger/input: User installs and launches the APK.
• Observable result: DEL launches on Android.
• Access state: Anonymous entry permitted.
• Failure/recovery: Install or launch failure surfaces an error; user may retry.
• Continuation: User proceeds to Landing.

FR-2 — Many live voice rooms (explicit) As a Room Participant / Listener, I should browse and enter many live voice rooms so that I can join live voice chat.

• Trigger/input: User opens Voice Rooms.
• Observable result: A list of live rooms with host, name and listener count is shown; entering a room joins its live voice chat.
• Access state: Established identity required.
• Failure/recovery: Load failure shows a retry; empty state offers Create Room.
• Continuation: User enters a room and participates.

FR-3 — Host creates and operates a live room (explicit) As a Room Host, I should create and operate a live room so that multiple participants can join my voice chat.

• Trigger/input: Host opens Create Room and submits a room name.
• Observable result: The room goes live and appears in Voice Rooms; the host sees the listener roster.
• Access state: Established identity required; hosting is role-restricted.
• Failure/recovery: Creation failure shows a retry; a dropped room can be re-opened.
• Continuation: Host runs the room and receives gifts.

FR-4 — Gambling/ampou bonus feature (explicit) As a Room Participant / Listener, I should claim ampou bonus rewards so that I receive bonus value in the app.

• Trigger/input: User opens Bonus Rewards and claims an available bonus.
• Observable result: The bonus is credited to the wallet and appears in claim history.
• Access state: Established identity required.
• Failure/recovery: "Bonus gagal diklaim" or "Bonus sudah diklaim" is shown; user may retry or return later.
• Continuation: User spends the credited value in rooms, gifts, chat, calls or the lucky draw.

FR-5 — Unlimited diamond and coin balance for the owner's account (explicit) As a Coin/Diamond Trader, I should hold an unlimited diamond and coin balance on the owner's account so that I can spend and transfer without depletion.

• Trigger/input: Owner opens Wallet.
• Observable result: The owner's diamond and coin balances display as unlimited; spending and transfers do not deplete them.
• Access state: Established identity required; the unlimited state applies only to the owner's account.
• Failure/recovery: Balance load failure shows a retry.
• Continuation: Owner proceeds to transfer coins or buy gifts.

FR-6 — Sell and transfer coins to other users (explicit) As a Coin/Diamond Trader, I should sell and transfer coins to another selected user so that value moves between accounts.

• Trigger/input: User opens Coin Transfer, selects a recipient user and enters an amount.
• Observable result: Coins move from the sender to the recipient and the transfer appears in history.
• Access state: Established identity required; transfer is role-restricted.
• Failure/recovery: "Saldo tidak cukup" or "Transfer gagal" is shown; user may correct and retry.
• Continuation: Recipient sees the received coins in their Wallet.

FR-7 — Premium gifts: frames and vehicles, priced expensively (explicit) As a Room Participant / Listener, I should send premium frames and vehicles priced expensively so that I can show status in a room.

• Trigger/input: User opens Room Gifts, selects a frame or vehicle and a recipient.
• Observable result: The gift arcs to the recipient with a pink shockwave ring and a gold price tag; the expensive price is deducted.
• Access state: Login required.
• Failure/recovery: "Saldo tidak cukup" or "Gift gagal terkirim" is shown with the selection retained.
• Continuation: User may top up via Wallet or send another gift.

FR-8 — Purchase and equip frames and vehicles (explicit) As a Coin/Diamond Trader, I should purchase and equip frames and vehicles so that I own and display premium items.

• Trigger/input: User opens Gift Collection and purchases or equips an item.
• Observable result: The item is owned and, when equipped, reflected on the avatar.
• Access state: Established identity required; role-restricted.
• Failure/recovery: "Pembelian gagal" or "Saldo tidak cukup" is shown; user may retry or top up.
• Continuation: User sends the equipped item as a gift or keeps it displayed.

FR-9 — Chat charged per message (explicit) As a Room Participant / Listener, I should send chat messages charged per message so that I can talk in text inside a room.

• Trigger/input: User composes and sends a message in Room Chat.
• Observable result: The message appears in the room chat and the per-message charge is deducted.
• Access state: Established identity required; role-restricted.
• Failure/recovery: "Saldo tidak cukup" or "Pesan gagal terkirim" is shown with the draft retained.
• Continuation: User may top up via Wallet or resend.

FR-10 — Video call charged per call (explicit) As a Room Participant / Listener, I should start and conduct video calls charged per call so that I can have paid face-to-face interaction.

• Trigger/input: User opens Video Calls, selects a recipient and starts a call.
• Observable result: The call connects and the per-call charge is applied.
• Access state: Established identity required; role-restricted.
• Failure/recovery: "Saldo tidak cukup" or "Panggilan gagal tersambung" is shown.
• Continuation: User may top up via Wallet or retry the call.

FR-11 — Lucky draw / jackpot (JP) (explicit) As a Room Participant / Listener, I should play the lucky draw / jackpot so that I can win JP prizes.

• Trigger/input: User opens Lucky Draw and spins the JP wheel.
• Observable result: The wheel spins with real deceleration; the winning segment floods the screen with gold for 600ms and the result settles.
• Access state: Established identity required; role-restricted.
• Failure/recovery: "Saldo tidak cukup" or "Spin gagal" is shown.
• Continuation: User may spin again or return to rooms.

FR-12 — Self-service account enrollment (required_inference) As a Room Host, I should create my own DEL account so that I can start using rooms, balances and gifts.

• Trigger/input: Anonymous visitor opens Sign Up and submits enrollment details.
• Observable result: A durable account is created and identity is established.
• Access state: Anonymous entry; protected state remains unavailable until identity is established.
• Failure/recovery: Field validation or "Pendaftaran gagal" is shown with the form retained.
• Continuation: User is routed to the destination they were attempting to reach.

FR-13 — Returning-user verification (required_inference) As a Room Participant / Listener, I should verify my identity on return so that I can reach my durable balances, rooms, gifts, calls and transfers.

• Trigger/input: Returning user opens Login and submits credentials.
• Observable result: Identity is established and the user reaches the intended protected destination.
• Access state: Anonymous entry; protected destinations remain unavailable until verification succeeds.
• Failure/recovery: "Kredensial tidak valid" is shown inline with the form retained.
• Continuation: User corrects and resubmits, or switches to Sign Up.

FR-14 — Durable backend execution (required_inference) As a Room Host, I should have my accounts, rooms, balances, charges, gifts, transfers, jackpot activity and bonus claims durably stored so that my state survives across sessions.

• Trigger/input: Any protected action (room creation, gift send, chat, call, transfer, spin, claim).
• Observable result: The action's state change is persisted and reflected on the next visit.
• Access state: Established identity required.
• Failure/recovery: Persistence failure surfaces an error and the action is not silently lost.
• Continuation: User retries the action.

FR-15 — Role-aware authorization for hosting and differentiated shared-state controls (required_inference) As a Room Host, I should have hosting and other materially differentiated shared-state controls restricted to my role so that room operation stays correct.

• Trigger/input: A user attempts a role-restricted action (create/operate room, transfer, spin, claim, send paid chat/call).
• Observable result: Authorized users complete the action; unauthorized attempts are refused.
• Access state: Established identity required; role-restricted surfaces enforce their role.
• Failure/recovery: Refusal surfaces a clear message; the user may return to an allowed surface.
• Continuation: User continues with permitted actions.

4. User Personas

Room Host

• Product context: Runs the many live voice rooms that make DEL loud. Hosting is a recurring responsibility, not a one-off action.
• Primary goal: Keep rooms active and monetized.
• Distinct accepted responsibilities: Creates and operates live rooms; keeps a room live for multiple participants; receives gifts sent by listeners and traders.
• Relevant inputs or decisions: Room name; when to open and when to end a room; how to keep the room busy.
• Interactions with other accepted participants: Listens to Room Participants / Listeners in the room; receives gifts from listeners and Coin/Diamond Traders; may send paid chat and start paid video calls.
• Observable success: A busy room where listeners send paid gifts and chat/video-call interactions.
• Constraints: Hosting is role-restricted; an established identity is required.

Room Participant / Listener

• Product context: Joins the many voice rooms to listen and take part in voice chat, and spends balance on gifts, chat, calls and the lucky draw.
• Primary goal: Engage in rooms and interactions using their diamond/coin balance.
• Distinct accepted responsibilities: Browses and enters rooms; sends gifts to hosts and other users; sends paid chat messages; starts paid video calls; plays the lucky draw; claims ampou bonus rewards.
• Relevant inputs or decisions: Which room to enter; which gift to send and to whom; whether to spend on a message, a call or a spin.
• Interactions with other accepted participants: Sends gifts to Room Hosts and other listeners; chats and video-calls with them; receives coins from Coin/Diamond Traders.
• Observable success: Engaging in rooms and interactions using their balance.
• Constraints: Protected destinations require an established identity; chat is charged per message and video calls per call.

Coin/Diamond Trader

• Product context: Holds an account with unlimited diamonds and coins, moves value to other users, and buys expensive gifts.
• Primary goal: Move coins to other users and spend them on premium gifts.
• Distinct accepted responsibilities: Sells and transfers coins to other users; buys expensive frames and vehicles; sends premium gifts.
• Relevant inputs or decisions: Which user to transfer to; how many coins to move; which expensive frame or vehicle to buy.
• Interactions with other accepted participants: Transfers coins to Room Participants / Listeners and Room Hosts; sends premium gifts into rooms.
• Observable success: Coins moved to other users and spent on premium gifts.
• Constraints: The unlimited diamond and coin balance applies to the owner's account; transfer is role-restricted.

5. Core User Flows

Flow A — Room Host creates and runs a live room

1. Host launches DEL and lands on Landing (anonymous).
2. Host taps Sign Up (or Login if returning) and establishes identity.
3. Host opens Create Room, enters a room name and creates the room.
4. The room goes live and appears in Voice Rooms; the host sees the listener roster.
5. Listeners enter; the host talks with them in live voice chat.
6. A listener or trader sends a gift; the host sees the gift arc land with a pink shockwave ring and a gold price tag.
7. A listener sends a paid chat message or starts a paid video call; the host responds.
8. Failure/recovery: If room creation fails, the host retries; if the room drops, the host re-opens it.
9. Continuation: The host keeps the room active and monetized, or ends the room and returns to Voice Rooms.

Flow B — Room Participant / Listener joins, gifts, chats and calls

1. Listener launches DEL and lands on Landing.
2. Listener taps Masuk Room; if no identity exists, Login is shown, otherwise Voice Rooms.
3. Listener browses the living-pill room capsules and enters a room.
4. Listener opens Room Gifts, selects a frame or vehicle at its expensive price and a recipient, and sends it.
5. The gift arcs across the room and lands with a pink shockwave ring; the price is deducted.
6. Listener opens Room Chat and sends a message; the per-message charge is deducted and the message appears.
7. Listener opens Video Calls, selects a recipient and starts a call; the per-call charge is applied on connection.
8. Failure/recovery: "Saldo tidak cukup" or a send/connect failure is shown with the draft or selection retained; the listener tops up via Wallet or retries.
9. Continuation: Listener returns to the room or browses other rooms.

Flow C — Room Participant / Listener plays the lucky draw and claims bonus

1. Listener opens Lucky Draw (or taps the gold Lucky JP capsule on Landing).
2. Listener spins the JP wheel; the liquid disc spins with real deceleration.
3. The winning segment floods the screen with gold for 600ms and the result settles.
4. Listener opens Bonus Rewards and claims an available ampou bonus.
5. The bonus is credited to the wallet and appears in claim history.
6. Failure/recovery: "Saldo tidak cukup", "Spin gagal", "Bonus gagal diklaim" or "Bonus sudah diklaim" is shown; the listener tops up or returns later.
7. Continuation: Listener spends the credited value in rooms, gifts, chat, calls or further spins.

Flow D — Coin/Diamond Trader transfers coins and buys premium gifts

1. Trader opens Wallet and sees the owner's unlimited diamond and coin balances as oversized gold numerals.
2. Trader opens Coin Transfer, selects a recipient user and enters an amount.
3. Trader confirms; coins move to the recipient and the transfer appears in history.
4. The recipient sees the received coins in their Wallet.
5. Trader opens Gift Collection, purchases an expensive frame or vehicle and equips it.
6. Trader enters a room and sends the premium gift via Room Gifts.
7. Failure/recovery: "Saldo tidak cukup", "Transfer gagal" or "Pembelian gagal" is shown; the trader corrects the amount or recipient and retries.
8. Continuation: Trader continues moving coins or buying gifts.

6. Visuals Colors and Theme

Muse: Karim Rashid. Headline: Sensual pop minimalism for a loud, glossy voice-room economy.

The direction is authoritative for this section. Tokens:

• Mode: Dark.
• Background: #160B22 (deep plum-black ground).
• Surface: #26103A (glossy plum surface) with border #334155-equivalent plum stroke; specular highlight arcs on top-left of every raised surface.
• Text: #FFF6FB (near-white pink-tinted body); secondary/muted #B79BC9.
• Primary: #FF2E9A (hot bubblegum pink) — every CTA, live-room dot, active capsule, balance chip.
• Accent: #FFD84D (lemon-gold) — reserved strictly for jackpot, ampou bonus and JP moments; never ordinary buttons.
• Gift artwork only: Lime #B4FF3A, tangerine #FF7A1A.
• Proportion: ~70% plum ground, 20% pink, 7% gold, 3% other candy. Never pink text on gold or gold on pink at body size.
• Headings font: Unbounded, 600–800 weight, tight -0.02em, used enormous — the coin balance, room titles and the word DEL are display objects.
• Body font: Quicksand 500/600, line-height 1.6, letter-spacing +0.01em.
• Type scale: 1.333 modular — display clamp(44px, 9vw, 96px); balance numerals 40px mobile / 72px desktop; section head 28px / 40px; card title 20px / 24px; body 15px / 17px; micro-label 11px / 12px uppercase +0.14em.

• Shape language: Capsules and pills for every control (radius = half height); 28–40px blob radii on cards; section boundaries cut as soft waves or arcs; 3D blob props (torus, capsule, teardrop) as recurring vocabulary. No sharp corners except the 2px hazard ticker at the very top.
• Spacing rhythm: Roomy, arc-separated sections; generous padding inside capsules and slabs.
• Imagery style: Glossy 3D candy-plastic props — diamond, coin stack, jet, sports car, crown, rocket, ring, teardrop — each with a visible specular highlight and soft pink ambient bounce on plum grounds or inside curved frames. Avatar frames are thick glossy torus/hexagon/petal rings in pink, gold and lime. No photography of people, no stock, no flat icon sets.
• Layout: Mobile-first single column at 375px with a thumb-zone bottom capsule dock (Rooms · Gifts · Lucky · Wallet); two-column arc grid at 768px with a sticky wallet ribbon; 12-column asymmetric editorial grid at 1280px with the live-room capsule grid full-bleed right and the wallet/transfer panel as a curved glass slab on the left.

7. Signature Design Concept

The public entry is a full-bleed plum void where the DEL wordmark is built as a glossy 3D pink capsule-sculpture bleeding off the right edge at 1280px and scaled and re-centred at 375px so the wordmark and the CTA stay wholly inside the viewport. Under it sits an oversized live counter — "12,480 rooms live" — in Unbounded at clamp(44px, 9vw, 96px), with the number in gold and the words in near-white. Directly beneath, a single horizontal scrolling row of live room capsules (host avatar ring, room name, listener count) drifts slowly leftwards and can also be dragged; the row may cross the viewport edge by design, but every capsule becomes fully readable as it passes. The primary CTA is one fat pink capsule, "Masuk Room", pinned bottom-left with the gold "Lucky JP" capsule beside it. There is no centred headline-subtext-button stack and no gradient blob: the composition is a diagonal cascade from the top-right wordmark down to the bottom-left CTAs, with a lime rim-light arc cutting across the lower third.

This concept only recomposes accepted content, states and controls — the wordmark, the live-room count, the room capsules and the two entry CTAs.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d

Landing Hero Motion Brief

• Focal subject: The glossy 3D pink DEL capsule-sculpture wordmark, with the oversized gold live-room counter beneath it.
• Input → transformation → outcome thesis: As the user drags or lets the room capsule row drift, the capsules slide leftwards and each becomes fully readable as it passes; the live counter's digits roll individually as the count changes; the wordmark's specular highlight slides across its surface. The outcome is a first frame that reads as a live, lucky, glossy marketplace of attention.
• Motion vocabulary: 320–520ms cubic-bezier(0.22, 1, 0.36, 1); capsules swell 1.0→1.04 on press with a glossy highlight that slides across; coin counts roll digit-by-digit; gift sends arc as tumbling 3D objects landing with a soft pink shockwave ring; the JP wheel spins with real deceleration easing; hover on desktop shifts the specular highlight, not the card.
• Composed first frame: Diagonal cascade from the top-right wordmark down to the bottom-left CTAs, with the drifting capsule row crossing the viewport edge and the lime rim-light arc across the lower third.
• Reduced-motion state: All motion collapses to instant state changes plus a single 200ms opacity fade; the room grid reflows into static rows and the capsule row becomes horizontally scrollable so every item can be brought fully into view.

9. Non-Functional Requirements

• NFR-1 — Android APK delivery (explicit): DEL ships as an Android APK. Rationale: explicit hard constraint.
• NFR-2 — App name (explicit): The app name is exactly DEL. Rationale: explicit hard constraint.
• NFR-3 — Durable state (required_inference): Accounts, rooms, balances, charges, gifts, transfers, jackpot activity and bonus claims must persist durably across sessions. Rationale: balances and transfers must remain bound to the correct participant.
• NFR-4 — Redis-backed runtime state (required_inference): Redis is required for live room presence, listener counts and ticking counters. Rationale: live-room capsules show pulsing live dots and ticking listener counts.
• NFR-5 — Readable text and controls at every viewport (explicit direction constraint): Headlines, wordmarks, labels, numbers, cards' text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling (for example font-size: clamp(...) with its mobile size) to fit; no other element covers any part of them. Imagery, decoration and motion may be cropped, bled, rotated, overlapped or cut as the direction asks, as long as they cover no readable text or control.
• NFR-6 — Reduced-motion support (explicit direction constraint): Under prefers-reduced-motion, motion collapses to instant state changes plus a single 200ms opacity fade, and the room grid reflows into static rows.
• NFR-7 — No blue/indigo, no white grounds, no flat icon sets (explicit direction constraint): No #2563EB/#6366F1 family, no bootstrap-blue CTAs on white, no white or near-white page grounds, no Inter/Roboto/Arial/Helvetica/Open Sans/Lato/Poppins/system-ui for headings or body, no flat or outlined line-art icons, no grid of identical hover-lift cards with grey borders and drop shadows, no centred SaaS hero, no gold on ordinary buttons, no photographic stock people as hero imagery.

10. Tech Stack

• Client: React Native (Android APK delivery).
• Backend: Python / FastAPI, extending a single shared backend process for accounts, rooms, balances, charges, gifts, transfers, jackpot activity and bonus claims.
• Storage: Durable primary datastore for accounts, rooms, balances, transfers, gifts, jackpot and bonus records.
• Cache / live state: Redis for live room presence, listener counts and ticking counters.
• Packaging: Docker / docker-compose for the backend and Redis services.

11. Assumptions and Constraints

• A-1: The unlimited diamond and coin balance applies only to the owner's account, as explicitly stated; other accounts hold ordinary balances.
• A-2: The gambling-adjacent bonus loop, unlimited owner balance and coin resale are implemented as in-app virtual-currency mechanics owned entirely by DEL; no external financial settlement, cash-out rail or third-party payment processor is introduced.
• A-3: Application-owned identity is required because balances, rooms, gifts, charges, transfers and jackpot activity are durable and must remain bound to the correct participant.
• A-4: Anonymous visitors may read the Landing surface; every protected destination requires an established identity.
• A-5: Role-aware authorization applies to hosting and other materially differentiated shared-state controls; it does not establish a broader permission system beyond what the accepted behavior requires.
• A-6: Gift prices for frames and vehicles are expensive by design, as explicitly stated.
• A-7: Chat is charged per message and video calls are charged per call, as explicitly stated.
• A-8: The page inventory is the closed, ordered page contract for this generation and is not extended.

12. Glossary

• DEL: The Android voice-room app delivered by this project.
• Voice Room: A live audio room hosted by a Room Host where multiple participants talk.
• Room Host: The persona who creates and operates live rooms.
• Room Participant / Listener: The persona who joins rooms, listens, gifts, chats, calls and plays the lucky draw.
• Coin/Diamond Trader: The persona who holds the owner's unlimited balance, transfers coins and buys expensive gifts.
• Ampou Bonus: The bonus reward feature users claim in Bonus Rewards.
• JP (Jackpot): The lucky draw feature played on the Lucky Draw page.
• Frame: A premium glossy avatar ring gift, priced expensively.
• Vehicle: A premium glossy vehicle gift, priced expensively.
• Diamond / Coin: The two in-app virtual currency balances held in the Wallet.
• Unlimited Balance: The owner's account state where diamond and coin balances do not deplete.
• Per-message charge: The coin cost deducted for each chat message sent in Room Chat.
• Per-call charge: The coin cost applied when a video call connects in Video Calls.