Build your own Airbnb.

# Build an original app inspired by Airbnb

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-stay rental marketplace called Stayfield, inspired by Airbnb. It is for a small inventory of hosts and guests in a controlled demo or pilot. The primary journey is publishing a listing, finding an available stay, and creating a conflict-free reservation request. Focus on one currency, date-based stays, and a transparent booking state machine.

## Design
Use an original listing grid with filters, a property detail page with original photos, a date-based price summary, and separate guest/host dashboards. Keep fees and cancellation state visible. A map is optional only if an actual provider is configured; never draw fake locations.

## Features
1. Listings: hosts create and edit title, description, photos they own, capacity, approximate location, amenities, and nightly price. Draft and published states are distinct and host ownership is enforced.

2. Availability and discovery: hosts block nights; guests filter by dates, capacity, and price. Display a consistent night-count and quote with all configured fees before booking.

3. Reservations: atomically prevent overlapping accepted or held stays, expire temporary holds, and support requested, accepted, rejected, canceled, and completed states with role-specific transitions.

4. Dashboards and messages: guests review requests and hosts accept/reject them. Provide booking-scoped messages and status history without exposing private host/guest details to other users.

5. Pilot scope: use a clearly labeled no-payment reservation flow initially. If payments are explicitly requested, use a real provider’s test environment and verified webhooks; never simulate successful charges or payouts.

## Tech stack
Use Django with PostgreSQL for a new backend and TypeScript for the frontend. Use server-side authorization, transactional reservation constraints, object storage for photos, and explicit timezone/date handling. Keep pricing and availability calculations on the backend. Preserve an existing suitable framework when present. Do not claim that listing software resolves payment, insurance, host verification, or local rental requirements.

## Data & behavior
User; HostProfile; Listing; ListingPhoto; AvailabilityBlock {listingId, startDate, endDate}; Quote {currency, nights, nightlyRate, fees, total, expiresAt}; Reservation {listingId, guestId, dateRange, status, holdExpiresAt, quoteSnapshot}; BookingMessage; Activity. Treat checkout dates as exclusive and protect occupancy constraints in the database.

Acceptance checks and scope:
Test two guests reserving the same dates, inclusive/exclusive date boundaries, blocked nights, hold expiry, stale price quotes, unauthorized host edits, cancellation, and image upload errors. Exclude real money, payouts, external calendar sync, tax engines, public reviews, and global inventory from the first 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.