Build a Tinder Clone App in Swift with AI

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

Screens and flows (light theme with your own warm gradient accent, not red-orange; bottom bar: Discover, Explore, Likes, Chats, Profile):
1. Discover: header with the Sparkr logo, a filters button (opens a sheet with distance and age range sliders and "Show me" selector) and a notifications bell. A deck of 12 profile cards (images.unsplash.com portrait photos, 3 photos per person, curl-checked): full-bleed rounded photo, photo segment bars at the top (tap the left or right side of the photo to switch photos), a bottom gradient with name and age ("Sofia, 26"), a "Recently active" green dot, "3 miles away", job or school, and 3 interest chips. An info button flips/expands into the full profile (bio, "Looking for" card, interests, basics, a music anthem, two prompts with answers, more photos), scrollable, with a down arrow to return.
2. Swiping: drag the top card in any direction; it rotates with the drag, and "LIKE" (right), "NOPE" (left) and "SUPER LIKE" (up) stamps fade in by direction; past a threshold it flies off with momentum, otherwise it springs back. The next card scales up from behind. Bottom button row: rewind (brings back the last card), nope, super like, like, boost; buttons fling the card with the same animation.
3. Matches: profiles #2, #4 and #7 in the deck like you back. Liking them triggers a full-screen "It's a Match!" overlay: both photos tilted and overlapping with a burst animation, "You and Sofia have liked each other", a "Say something nice..." input with a send button, and "Keep swiping". Sending opens the chat.
4. Chats: "New Matches" horizontal row (new matches appear here live), then the message list with last message, time and unread badges. A chat thread has the match's photo header, bubbles, a "You matched on Oct 8" marker, a GIF button, and a send box; sending a message makes the match reply after a short "typing..." indicator with a fixture reply.
5. Likes: "18 likes" grid of blurred cards with a Gold upsell banner; tapping one shows an upsell sheet. Explore: themed tiles ("Looking for Love", "Free Tonight", "Coffee Date", "Gamers") that open a smaller deck.
6. Profile: your avatar with a profile completion ring "62% complete", Edit profile (photos grid with + slots, bio, interests editor), settings rows, and a premium tiers carousel.
7. When the deck runs out show "You've seen everyone nearby" with a "Start over" button that resets the deck.

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