Build your own Zoom.

# Build an original app inspired by Zoom

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 meeting app called Gatherroom, inspired by Zoom. It is for scheduled meetings of up to four participants in a controlled pilot. The core journey is creating a meeting, joining through a link, admitting attendees from a waiting room, talking through real media, and ending the meeting. Make the small supported limit explicit.

## Design
Create an original meeting dashboard and pre-join device check, followed by a video grid with readable participant names and a persistent control bar. Distinguish host-only controls, local mute state, admission status, and connection errors. Provide a keyboard-accessible participant list and chat.

## Features
1. Scheduling: create a titled meeting with start time/timezone, generate an unguessable invitation token, copy a join link, cancel the meeting, and distinguish expired or revoked links.

2. Pre-join and waiting room: preview camera/microphone, enter a display name, request admission, and let the authorized host admit or reject attendees. Unadmitted users must never receive room chat or media signaling.

3. Media: connect up to four users through a documented WebRTC topology, support mute/camera-off and active sharing selection, and show genuine connection states. Use a configured relay/SFU or explicitly bounded mesh.

4. Host controls and chat: remove a participant, lock the room, stop a screen share, send meeting chat, and end the meeting for everyone. A host mute can request remote muting; never covertly enable another person’s microphone.

5. Recovery: handle a temporarily disconnected host, reconnect participants within a short grace period, prevent duplicate participant identities, and clean up tracks, room presence, and invitations after the end state.

## Tech stack
Use TypeScript with authenticated meeting APIs, PostgreSQL, WebSocket signaling, and WebRTC. Prefer an available maintained media service/SFU; a four-person mesh is acceptable only with documented limits and TURN support. Screen sharing must be user-triggered. Verify media infrastructure separately from meeting metadata.

## Data & behavior
User; Meeting {hostId, title, startsAt, timeZone, state, locked}; Invite {tokenHash, expiresAt}; Participant {admissionState, role, lastSeenAt}; MediaSession; ChatMessage; HostAction. Persist host permissions and room lifecycle on the server; do not trust a participant-supplied role.

Acceptance checks and scope:
Test host and three attendees, denied device access, waiting-room denial, unauthorized host commands, revoked links, interrupted screen share, reconnect, and end-for-all cleanup. Exclude recording, webinars, breakout rooms, calendar integrations, and large conferences.

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