Build an Airbnb Clone App in Swift with AI

Build a polished, fully working native iOS app in SwiftUI named Nestly: an original vacation-rental booking app that recreates the core experience of Airbnb, but with its own name, its own original logo and its own color palette. Do NOT use the Airbnb name, logo, wordmark, app icon or any trademarked asset anywhere in the app. Design an original Nestly logo mark, drawn with SwiftUI shapes (Path/Canvas) or made as a generated image asset, and use it in the header.

Screens and flows (bottom tabs: Explore, Wishlists, Trips, Inbox, Profile; light theme, your own accent color for primary buttons):
1. Explore: a floating search pill "Where to?" with "Anywhere · Any week · Add guests", a horizontally scrolling category bar with icons and labels (Beachfront, Cabins, Amazing views, Tiny homes, Treehouses, Lakefront, Countryside, Design, Castles) with an animated underline; switching category swaps the listings with a fade. Listing cards: full-width photo carousel (swipe, page dots, 4-5 photos per stay), heart button that toggles into a Wishlist with a toast, "Guest favorite" badge on some, title like "Cabin in Big Bear Lake, California", "Hosted by Elena", dates "Nov 3 – 8", "$248 night · $1,240 total", rating "4.96". At least 14 stays across categories.
2. Map: a floating "Map" button switches to a SwiftUI MapKit Map (no location permission) with price-pill annotations at each stay's fixture coordinate; tapping a pill highlights it and slides up that listing's card; "List" switches back.
3. Search: tapping the pill opens a full-screen modal with three steps: Where (search input and suggested destinations), When (calendar to pick a date range with highlighted range), Who (Adults, Children, Infants, Pets steppers). "Search" filters results and updates the pill text.
4. Listing detail: photo carousel header with back, share and heart, title, "Entire cabin · 4 guests · 2 bedrooms · 3 beds · 2 baths", rating and reviews count, host row (photo, "Hosted by Elena · Superhost · 6 years hosting"), 3 highlights, description with "Show more", "What this place offers" amenities, reviews carousel with a rating breakdown, a small non-interactive MapKit location map, house rules. Sticky bottom bar with price, dates and a "Reserve" button.
5. Booking: "Reserve" opens "Confirm and pay": trip dates and guests (editable), price breakdown ($248 x 5 nights, cleaning fee, service fee, taxes, total), payment method "Visa •••• 4242", "Confirm and pay" with a short processing state, then a "You're going to Big Bear Lake!" success screen with a celebration animation; the trip shows up in Trips.
6. Wishlists: grid of saved stays (updates live from hearts). Trips: upcoming and past trips with photos and dates. Inbox: host messages; open a thread and send. Profile: avatar, "Show profile", settings rows.

Rules for the whole app:
- Native SwiftUI for iOS 26, the deployment target the Vibecode iOS template already uses (do not change it). iPhone-first layout. SF Symbols are fine for UI icons (never for the Airbnb logo or any brand mark).
- Everything runs on-device from realistic, deterministic fixture data in one Swift file (e.g. Fixtures.swift: real-sounding names, handles, numbers, timestamps, captions). No backend (leave the backend/ folder alone and make no network calls except loading images and media), no login, no permissions (no camera, photos, location, contacts, notifications, microphone). Do not persist state (no UserDefaults, @AppStorage, SwiftData or files): every launch starts from the same fixture state, so the demo is repeatable.
- Remote images: load images.unsplash.com photo URLs (with ?w=800&q=80 style params) with AsyncImage (or a small cached image view) and a tasteful placeholder. Verify every image and media URL with `curl -s -o /dev/null -w "%{http_code}" <url>` before you use it and replace any that do not return 200. No broken or blank images anywhere.
- Polish: native-feeling spacing and typography, safe areas, smooth spring animations (.spring/.snappy, most under 350 ms), matchedGeometryEffect for hero and expand/collapse transitions where it helps, .sensoryFeedback haptics on key taps, pressed states, and loading/empty states. Simulated waits stay short (under 3 s). Every button visible on screen does something sensible; nothing is a dead end.
- Keep the compiler happy: small files (under ~300 lines each), big view bodies split into subviews, and no long chained expressions, so nothing hits "unable to type-check this expression in reasonable time".
- It must build with zero errors and run in the iOS simulator with no crash. Walk through every flow above and fix anything broken.