Build your own Chatroulette.

# Build an original app inspired by Chatroulette

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 video conversation app called Roundabout, inspired by Chatroulette. It is for a controlled community pilot of consenting adults. The main flow is checking devices, joining a moderated matching queue, talking to one matched participant, and immediately leaving or skipping. Reliable matching, device cleanup, and accountability are core product features.

## Design
Use an original video-first layout with a prominent remote feed, a smaller local preview, and a persistent control strip for next, stop, mic, camera, report, and block. Make waiting, connecting, disconnected, and moderation states explicit. Use an accessible high-contrast palette and a mobile layout that retains every exit control.

## Features
1. Session and devices: establish an accountable pseudonymous session, adult eligibility appropriate to the pilot, and explicit rules/consent. Let users preview and mute their camera/microphone before joining.

2. Pairing: maintain a server-side eligible queue, reserve pairs atomically, avoid recent or blocked peers where practical, and reject multiple concurrent matches for a user.

3. Video connection: implement WebRTC offer/answer/ICE exchange authorized to a live match, supported STUN/TURN configuration, connection timeouts, and retry states. Expose relay failure clearly.

4. Skip and cleanup: skip, stop, or disconnect cancels the old match generation, tears down peer connections and tracks, and optionally rejoins the queue after user consent. Old signaling must not attach to the new peer.

5. Moderation: implement reports, blocks, moderator review, bans, queue rate limits, and a narrowly scoped audit log. Public release requires staffed moderation and a verified eligibility/privacy process.

## Tech stack
Use a Go backend for sessions, matchmaking, and WebSocket signaling, with a TypeScript browser interface and WebRTC peer connections. Use PostgreSQL for durable moderation records and a queue/store suitable for atomic matching. Issue short-lived TURN credentials server-side and define deployment behavior for multiple instances. A local demo may connect two browser sessions but must be labeled as such.

## Data & behavior
Account; DeviceConsent; Session; QueueEntry; Match {id, sessionA, sessionB, generation, state, createdAt, expiresAt}; Block; Report; Ban; ModeratorRole; AuditEvent. Do not record media or expose counterpart IP addresses in the interface. Keep signaling and moderation access separately scoped and minimize retained metadata.

Acceptance checks and scope:
Verify two-user connection on different networks where available, next/next races, camera denial, relay-only connectivity, reconnect, moderator bans, and complete media cleanup on stop. Do not claim successful internet connectivity from a same-machine demo. Exclude recordings, gifts, subscriptions, location discovery, and unmoderated public access.

## 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.