Build your own Google Meet.

# Build an original app inspired by Google Meet

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 instant meeting app called Quickroom, inspired by Google Meet. It is for two-to-four people joining a browser call from an invitation link. The primary journey is creating an instant room, checking devices, admitting another participant, and sharing a screen. Prioritize a reliable join flow over a scheduling suite.

## Design
Use an original clean pre-join screen with camera preview and readable device status, followed by a responsive tile layout and consistent bottom controls. Show who is sharing, who is muted, whether the room is locked, and whether the connection is reconnecting. Provide visible captions only when real caption data exists.

## Features
1. Instant rooms: create an unguessable short-lived room, copy its invitation, admit guests with bounded display names, and let the owner lock or end it. Do not treat knowing a room ID as authorization for owner actions.

2. Device readiness: explicitly request microphone/camera permission, select supported devices, join audio-only when needed, and provide useful help when a device is absent or permission is denied.

3. Small-group calls: establish real WebRTC connections for a documented maximum of four users, indicate connection quality from actual states, mute locally, toggle camera, and leave without disturbing the others.

4. Screen sharing and chat: share a user-selected display/window, switch the main stage to the active share, handle the browser stop-sharing control, and exchange meeting-only text chat. Caption file import or configured live transcription is optional and labeled accurately.

5. Lifecycle: recover from temporary reconnects, remove inactive guests after a grace period, prevent duplicate presence, and stop every media track when leaving, navigating away, or ending a room.

## Tech stack
Use TypeScript, an authenticated room API, WebSocket signaling, and WebRTC with configured STUN/TURN or an available media service. Keep the bounded room state authoritative on the server. If using a mesh, explain its four-person limit. Do not implement fake captions, screen sharing, or internet connectivity.

## Data & behavior
Room {ownerId, tokenHash, expiresAt, locked, state}; Participant {id, roomId, admissionState, lastSeenAt}; SignalingSession; ChatMessage; ShareState. Persist necessary room metadata and expire ephemeral meeting content according to a documented policy. Do not store captured audio/video.

Acceptance checks and scope:
Test two-to-four devices, audio-only join, permission denial, waiting guest access, screen-share termination, reconnect, and media cleanup after navigation. Exclude Google Calendar/account integration, meeting recording, translation, and unsupported automatic captions.

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