Build your own Netflix.

# Build an original app inspired by Netflix

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 streaming-library app called Screenroom, inspired by Netflix browsing and playback workflows. It serves a household or small authorized audience watching owned or licensed video. The main journey is selecting a profile, finding a title, adding it to a watchlist, watching it, and resuming later. Do not provide or scrape Netflix titles, media, artwork, or accounts.

## Design
Create an original cinematic but readable browse experience with accessible horizontal shelves, original title artwork, a detail page, and a working player. Keep profile selection, episode ordering, subtitles, audio controls, and Continue Watching distinct. Respect reduced motion and do not autoplay sound on page load.

## Features
1. Library management: authorized administrators add permitted films or series, original descriptions/posters, episode order, duration, and playable asset references. Validate files and show processing or unavailable states honestly.

2. Profiles: create a few profiles under an authenticated household account, select an active profile, and keep each profile’s preferences, watchlist, and viewing progress separate. Do not imply a profile selector is a security boundary between unrelated accounts.

3. Browse and search: build curated genre/title shelves, search permitted metadata, open title details, and add/remove a profile watchlist. Recommendations begin as explicit curated or genre-matched rows.

4. Playback and resume: play a documented supported stream/file, seek, select provided captions, persist progress periodically and on pause/exit, and resume only after user action. Mark completion using an explicit threshold and offer the next episode with a cancelable countdown.

5. Access and recovery: authorize playback asset requests, handle buffering/missing codecs/expired URLs, allow removing a title from Continue Watching, and keep progress updates monotonic under retries where appropriate.

## Tech stack
Use a TypeScript app/API with PostgreSQL, private object storage, and a configured media-processing service if transcoding is needed. Start with supported MP4 or HLS assets and verified caption files. Use authorized short-lived playback URLs, lazy-load posters, and serve media through suitable infrastructure. This is a permitted library, not a Netflix service integration.

## Data & behavior
Account; User; Profile {accountId}; Title {kind, synopsis, genre, posterKey}; Season; Episode {position, assetId}; MediaAsset {rendition, duration, state}; CaptionTrack; WatchlistItem {profileId, titleId}; WatchProgress {profileId, assetId, seconds, completedAt, updatedAt}. Apply account authorization before trusting a profile ID.

Acceptance checks and scope:
Test separate profile watchlists/resume positions, expired playback URLs, caption synchronization, a completed episode, canceled next-episode autoplay, unauthorized accounts, and unavailable media. Use licensed samples. Exclude commercial catalogs, DRM guarantees, downloads for offline viewing, real subscriptions, and Netflix account 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.