Build your own YouTube.

# Build an original app inspired by YouTube

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 video publishing platform called Viewfoundry, inspired by YouTube. It is for a small set of creators uploading videos they own or have licensed. The main journey is uploading a video, waiting for verified processing, publishing it to a channel, and watching it through a working player. Begin with a curated library and explicit resource limits.

## Design
Create an original responsive browse page with channels, thumbnails, search, and a watch page with player, caption controls, description, and playlist context. Separate uploading, processing, failed, draft, and published states. Show actual duration and progress rather than simulated readiness.

## Features
1. Channels and permissions: authenticate creators, manage their channel description and artwork, and separate owner uploads from viewer actions. Public and unlisted videos must have explicit retrieval rules; unlisted is not private authorization.

2. Upload and processing: accept documented input formats within a size/duration quota, upload resumably if supported, inspect actual media, and queue a bounded transcoding/thumbnail job. Expose progress, failure, cancellation, and retry.

3. Playback: serve a supported playable rendition or configured adaptive stream, handle buffering and errors, support seeking and uploaded captions, and persist per-user resume position. Confirm the media works outside the upload preview.

4. Discovery and playlists: search published titles/tags, browse chronological channels, subscribe to channels, and create ordered personal playlists. Start with a transparent curated recommendation row.

5. Community and operations: allow bounded comments and reporting, moderate/remove videos and comments, track playback events with a documented counting rule, and clean up media when a video is deleted.

## Tech stack
Use TypeScript for the app/API, PostgreSQL, and scoped object storage. Put rendering in a separate bounded worker or managed media service, with a properly licensed configured encoder. Persist job state and idempotent callbacks. Serve large media efficiently and never perform arbitrary untrusted media processing inside a page request.

## Data & behavior
User; Channel; Video {ownerId, visibility, state, title, mediaKey, duration}; Upload; ProcessingJob; Rendition; CaptionTrack; Subscription; Playlist; PlaylistItem; WatchProgress; PlaybackEvent; Comment; Report. Enforce quotas and ownership at API/storage boundaries; derivative files retain the source video access policy.

Acceptance checks and scope:
Test upload/process/publish/watch from a second session, malformed media, worker failure/retry, seek/caption timing, private draft access, duplicate job callbacks, and deleted-file cleanup. Exclude the YouTube catalog, Content ID, advertising, live streaming, and large-scale recommendations.

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