Build your own Patreon.

# Build an original app inspired by Patreon

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 membership app called Supportcircle, inspired by Patreon. It is for a small set of creators publishing original work and inviting supporters to clearly defined tiers. The main journey is defining a tier, publishing a tier-only post, enrolling a supporter through a test subscription or explicit manual pilot, and verifying access. Use non-explicit original sample content.

## Design
Create an original creator page with a readable introduction, tier comparisons, visible billing/test status, and a post archive. Creators get a focused publishing dashboard; supporters see their active access and cancellation status. Show locked previews without leaking restricted content.

## Features
1. Creator setup: create a profile, define a small set of membership tiers with benefits and a single currency, publish/unpublish tiers, and keep archived tier access rules explicit.

2. Post publishing: compose original text, attach permitted bounded media, select public/free-member/tier access, schedule only if a real job system exists, and preview as each audience before publishing.

3. Membership lifecycle: enroll through a configured payment sandbox or clearly labeled manual approval. Track pending, active, canceled-at-period-end, expired, and failed states without trusting a frontend success redirect.

4. Access and engagement: enforce post/media permissions on the server, permit comments by an allowed audience, paginate the member feed, and notify members of newly published accessible posts in-app.

5. Creator operations: inspect actual members and entitlement periods, remove/report content, process duplicate webhook events idempotently, and allow supporters to cancel through the supported test or manual flow.

## Tech stack
Use PHP/Laravel, PostgreSQL, private object storage, and an official SDK for a configured payment provider’s sandbox. Keep entitlements derived from verified server-side payment events or explicit audited manual grants. Use expiring media URLs after access checks. Live creator payouts are outside this pilot.

## Data & behavior
User; Creator; Tier {priceMinor, currency, active}; Membership {tierId, providerSubscriptionId, state, validUntil}; Post {creatorId, audience, minimumTierId, state}; Media; Comment; PaymentEvent {uniqueProviderId}; Entitlement; ModerationAction. Cancellation policy must say whether access continues through validUntil.

Acceptance checks and scope:
Test tier-only content as member/nonmember, direct media access, cancellation at period end, payment failure, duplicate/out-of-order webhooks, unpublished tiers, and manual approval if no provider exists. Exclude real payouts, tax handling, merchandising, licensed creator media, and unconfigured subscriptions.

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