Build your own TikTok.

# Build an original app inspired by TikTok

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 short-video community called Looplane, inspired by TikTok. It is for a controlled group publishing original vertical clips up to a documented short duration. The primary journey is uploading a clip, processing and publishing it, following the creator, and viewing it in a responsive vertical feed. Begin with newest and following feeds instead of an opaque recommendation model.

## Design
Use an original full-height clip viewer with readable caption/creator overlays, clear mute/play controls, and an accessible alternative browse list. Pause offscreen videos, avoid playing several clips simultaneously, and keep reporting controls visible. Respect reduced motion and browser autoplay policies.

## Features
1. Creators and following: authenticate members, edit creator profiles, follow/unfollow, and block users. A block must affect feeds and direct viewing, not only hide a card.

2. Clip upload: accept owned clips within actual file/duration limits, inspect and process media with a configured worker, generate a poster, attach a caption or uploaded subtitle track, and expose draft/failed/published states.

3. Vertical playback: page through published videos with touch and keyboard controls, preload only a bounded next clip, pause hidden clips, and provide mute/seek controls. Preserve a stable current item when loading another page.

4. Interactions: toggle likes, comment on accessible clips, save private favorites, and show verified counts. Keep replay/view counting explicit and avoid counting every UI rerender as a view.

5. Moderation: report clips/comments, review/remove content, limit uploads/comments by account, and remove access to original and derived media when a clip is withdrawn.

## Tech stack
Use TypeScript, PostgreSQL, private object storage, and a separate bounded media-processing worker or available video service. Authenticate upload/publish operations, validate media, and use efficient streaming/poster delivery. Keep ordering deterministic and captions safe. Automatic transcription may be added only with a real configured service.

## Data & behavior
User; CreatorProfile; Follow; Block; Clip {ownerId, state, assetId, caption, duration}; ProcessingJob; Rendition; CaptionTrack; Like; Comment; Favorite; PlaybackEvent; Report; ModerationAction. Video deletion invalidates all published renditions and feed entries.

Acceptance checks and scope:
Test malformed/oversize clips, processing retry, one active player while swiping, denied autoplay, keyboard browsing, duplicate likes, blocked users, and media deletion. Exclude copyrighted music catalogs, face filters, duet remixing, live commerce, and recommendation-training claims.

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