Build an Uber Clone App in Swift with AI

Build a polished, fully working native iOS app in SwiftUI named Zipride: an original ride-hailing app that recreates the core experience of Uber, but with its own name, its own original logo and its own color palette. Do NOT use the Uber name, logo, wordmark, app icon or any trademarked asset anywhere in the app. Design an original Zipride 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: Home, Services, Activity, Account; clean light UI, black primary buttons, your own accent color):
1. Home: a full-screen SwiftUI MapKit Map of downtown San Francisco with a muted map style (no location permission: show a custom pulsing annotation at a fixed coordinate instead of the user's location) with a pulsing blue "you are here" dot and 5 small car annotations slowly driving along fixture street coordinates. Bottom sheet: "Where to?" search pill with a "Now" schedule chip, saved places (Home: 1458 Oak Street, Work: 200 Market Plaza), 3 recent destinations with distances, and service shortcuts (Ride, Reserve, Package, Rental).
2. Destination search: tapping "Where to?" opens a screen with pickup "Current location" and destination inputs; typing filters 12 fixture places (name, address, distance), plus suggestions before typing.
3. Ride options: choosing a place returns to the map, which draws an animated MapPolyline route from pickup pin to destination pin (MKDirections, with a fixture polyline fallback) and animates the camera to fit it. Bottom sheet lists ride types with car illustrations, seats, arrival time and price: ZiprideX $14.20 (4 seats, 3 min), Comfort $18.75, XL $24.10, Green $15.30, Black $32.40. Tapping selects with a highlight; payment row "Visa •••• 4242" opens a payment picker; big black "Choose ZiprideX" button.
4. Matching: confirm shows "Finding your driver" with a radar pulse on the pickup pin for about 3 s, then a driver is matched: card with driver photo, "Marcus", 4.92 star rating, "Toyota Camry · Gray", plate "8KJD372", call and message buttons, "Cancel ride". The driver's car annotation drives along the route coordinates to the pickup over about 8 s while the header counts down "Arriving in 3 min" to "Your driver has arrived".
5. Message button opens a chat sheet with quick replies ("I'm on my way", "I'm at the pickup spot"); sending shows the driver replying.
6. Trip: "Start trip" (or automatically after arrival) moves the car along the route to the destination over about 8 s with a trip progress bar and ETA; arrival opens a "How was your ride with Marcus?" screen with 5 tappable stars, tip chips ($1, $2, $5, Custom), and Done returns Home with the trip added to Activity.
7. Activity: past trips with mini route maps, date, price; tap for a receipt. Services: grid of service tiles. Account: profile, rating, wallet, 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 Uber 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.