Build your own Tinder.

# Build an original app inspired by Tinder

You are an experienced mobile product designer and mobile 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: iOS / Android. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original adult-only native matching app called Kindred, inspired by Tinder’s mutual-interest workflow. Use Flutter for a controlled iOS/Android pilot. Eligible participants create a profile, review consenting participants, express interest, and chat only after a mutual match. Start with a closed test community and coarse regions rather than precise live location.

## Design
Create original profile cards with accessible like/pass buttons alongside optional swipe gestures. Make age eligibility, profile visibility, match state, safety controls, and account deletion easy to find. Use inclusive profile fields and avoid displaying exact distance, home location, or sensitive profile details in notifications.

## Features
1. Eligibility and profiles: define and implement the pilot’s adult eligibility and account review process, consent to discovery, photo moderation, and editable profile fields. A checkbox alone is not a public-service eligibility system.

2. Discovery: show a bounded queue of eligible opted-in profiles using explicit preferences and broad regions. Exclude yourself, blocked accounts, and previously handled profiles; give users a way to pause discovery.

3. Mutual matching: persist like/pass decisions, create one match atomically when both accounts like each other, and avoid revealing unmatched likes or private preference data through APIs.

4. Match chat: allow private text messages only within an active match, implement pagination and reconnect deduplication, and immediately stop message access when either member unmatches or blocks.

5. Safety and removal: provide blocking, reports with a defined evidence policy, moderator review, photo removal, and account deletion. Enforce every restriction on the server and document retention and pilot oversight.

## Tech stack
Use Flutter/Dart with a TypeScript backend, PostgreSQL, private image storage, and an authenticated real-time transport. Enforce eligibility and match authorization on the server. Keep precise GPS and address-book data out of the MVP and test native lifecycle and photo permissions.

## Data & behavior
User {eligibilityState, discoverable}; Profile {region, fields}; Photo {reviewState}; Preference; Decision {actorId, targetId, outcome}; Match {canonicalPair, state}; Message; Block; Report; ModerationAction; DeletionJob. Ensure a unique active pair and restrict report evidence access.

Acceptance checks and scope:
Test simultaneous mutual likes, duplicate decisions, age/eligibility denial, paused discovery, blocked profile exclusion, chat after unmatching, and account deletion on mobile devices or emulators. Exclude exact-location tracking, minors, payments, matching AI, and unrestricted public launch. Document the eligibility and moderation setup required for the chosen pilot.

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