Build your own Omegle.

# Build an original app inspired by Omegle

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original adult-oriented random conversation app called Pairwise, inspired by the historical Omegle text/video matching workflow. It is for consenting adults in a controlled pilot community. The core journey is joining a queue, matching with another eligible participant, chatting, and choosing next or stop. Video is an explicit opt-in extension. This is not an affiliation with or revival of the reference service.

## Design
Use an original simple interface with a large text conversation, clearly separated local/remote video panels when enabled, visible connection state, and persistent next, stop, block, and report controls. Explain camera/microphone permission before requesting it. Make exit and mute immediately accessible and avoid engagement tricks that hide safety controls.

## Features
1. Entry and preferences: require authenticated or accountable pseudonymous sessions, an adult eligibility flow appropriate to the pilot, explicit community-rule acceptance, and optional broad topic interests. A checkbox alone is not sufficient for an unrestricted public launch.

2. Matching: implement an atomic server-side queue with one active match per participant, timeout/requeue handling, next/stop controls, and exclusions for blocked or banned participants. Do not expose another participant’s identifiers to the client.

3. Text chat: send bounded plain-text messages scoped to the current match, reject stale match IDs, handle reconnects, and show delivery/connection status. Set an explicit retention policy and do not silently store full transcripts.

4. Optional video: add WebRTC signaling with short-lived match-scoped tokens and configured STUN/TURN. Request devices only after opt-in, clean up tracks on every exit, and do not record calls.

5. Operations: provide block/report actions, rate limits, a moderator queue with restricted access, report outcomes, and server-enforced bans. Keep a controlled pilot until moderation, eligibility, and privacy operations are ready.

## Tech stack
Use TypeScript with a browser frontend, a Node.js signaling/API service, and transactional storage for sessions, matches, and moderation. Use an appropriate shared queue mechanism when running multiple server instances. Use WebRTC for optional peer media; TURN credentials must be short-lived and issued server-side. Do not fake matching with scripted peers or claim browser-only storage can operate a shared service.

## Data & behavior
Participant {id, eligibilityState, status}; Session {id, participantId, expiresAt}; QueueEntry {sessionId, mode, interests, queuedAt}; Match {id, participantIds, generation, state, expiresAt}; Block {ownerId, blockedId}; Report {id, matchId, reporterId, reason, minimalEvidence, status}; ModerationAction. Authorize all messages and signaling by current match and session. Minimize personal data and define report retention.

Acceptance checks and scope:
Test two participants, simultaneous next actions, disconnect/requeue, a blocked pair, expired signaling tokens, denied camera permission, and banned users attempting to rejoin. Confirm media stops after exit and moderator data is not public. Exclude recording, location-based discovery, payments, anonymous unlimited public access, and minors from the pilot scope.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.