Build your own OnlyFans.

# Build an original app inspired by OnlyFans

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 creator subscription app called Memberframe, inspired by OnlyFans-style creator feeds and paid access. The pilot uses non-explicit original creator content, one currency, and sandbox or audited manual entitlements. The primary journey is following a creator, obtaining a test subscription, opening a gated post, and optionally unlocking a one-time paid post.

## Design
Use an original creator profile and media feed with clear public previews, subscription status, individual unlock pricing, and a compact creator dashboard. Never place restricted media in hidden HTML or preload it before authorization. Make cancellation, reporting, and access expiry understandable.

## Features
1. Creator profiles: manage original profile information, bounded public previews, a subscription price, and a publication status. Distinguish creator and subscriber roles without exposing private member data.

2. Restricted media: upload owned supported images/video within quotas, validate files, create approved safe previews, and publish subscriber-only or individually unlockable posts. Private originals require authorized signed delivery.

3. Entitlements: activate a test subscription or audited manual grant, verify one-time post unlocks, handle expiry/cancellation, and show access state from the server. A client badge never grants access.

4. Member interaction: follow creators, comment on accessible posts, manage a private purchase/access history, and block/report abusive members or content. Keep explicit content and private-message monetization outside the pilot.

5. Operations: inspect real subscription/unlock states, make payment callbacks idempotent, revoke fraudulent manual grants with a logged reason, and remove media access when required. Provide a clear moderation queue and content policy.

## Tech stack
Use TypeScript, PostgreSQL, private object storage, and a configured payment sandbox with signed webhook verification. Model subscription and one-time entitlements separately. Check both membership and post-unlock rules on every content/media request. Do not collect raw card details or run real creator payouts in QA.

## Data & behavior
User; CreatorProfile; Follow; Subscription {state, validUntil}; Post {creatorId, accessType, unlockPriceMinor, state}; MediaAsset; PostUnlock {userId, postId, state}; PaymentEvent; AccessGrant; Comment; Report; ModerationAction. Store integer money amounts and immutable purchase snapshots.

Acceptance checks and scope:
Test preview versus restricted payloads, direct media URL denial, expired membership, an individual unlock after membership expires, duplicate payment events, canceled creator content, and role authorization. Exclude explicit-content operation, live payments/payouts, tipping, private pay-per-view messages, and protection claims against copying media.

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