Instagram clone

Build a polished, fully working native iOS app in SwiftUI named Pixgram: an original photo-sharing social app with its own name, its own logo and its own color palette. Design an original Pixgram logo mark, drawn with SwiftUI shapes (Path or Canvas) or made as a generated image asset, and use it in the header. Use no other company's name, logo, wordmark, app icon or trademarked asset anywhere in the app. Screens and flows. Bottom tab bar: Home, Explore, Create, Activity, Profile. Light theme: white background, near-black text, and a story-ring gradient of your own, sunset coral to violet. 1. Home feed. Header: the Pixgram wordmark in a script-style display font (a bundled .ttf or a drawn wordmark), a heart icon that opens Activity and a paper-plane icon that opens Messages. Stories row: "Your story" with a + badge, then 9 friends with gradient rings and usernames. Feed of 8 posts: avatar, username, a verified tick on two, location line, square or 4:5 photo, actions row (heart, comment, share, bookmark), "Liked by maya.lens and 1,284 others", caption with the username in bold and a "more" expander, "View all 36 comments", "2 hours ago". One post is a 3-photo carousel with swipe, page dots and a "1/3" pill. 2. Likes. Double-tapping a photo shows a big white heart that pops and fades over it and likes the post; the heart icon fills red with a bounce and the like count updates; tap again to unlike. The bookmark toggles filled. 3. Stories. Tapping a story ring opens a full-screen viewer: segmented progress bars at the top that fill over 5 s and advance on their own, avatar, name and time; tap the right half for next and the left half for previous; at the end it moves on to the next friend's stories; swipe down or X to close; a "Send message" reply bar with heart and send. Viewed rings turn grey in the stories row. 4. Comments. The comment icon opens a bottom sheet with 12 comments (avatars, likes on comments, reply links), an emoji quick bar and an input; posting adds your comment at the top with an animation. 5. Explore. A search bar and a 3-column photo grid with a few 2x2 tiles; tapping a tile opens that post in a scrollable feed. Typing in search shows matching accounts. 6. Create. Pick a photo from a sample gallery grid (12 photos), go on to a caption screen; Share puts the new post at the top of Home with a short "Posted" toast. 7. Activity. "Today" and "This week" sections of likes, follows (the Follow button toggles to Following) and comments. 8. Profile (ansh.shoots): avatar with a story ring, posts / followers / following counts, name, bio with a link, Edit profile and Share profile buttons, a story highlights row, grid / reels / tagged tabs and a 3-column grid of 15 posts. 9. Messages. A list of 8 chats with online dots; tapping one opens a thread with bubbles; sending a message appends it and the other person replies after a short typing indicator. Rules for the whole app: - Native SwiftUI for iOS 26 (keep the project's deployment target). iPhone-first layout. SF Symbols are fine for UI icons, never for the Pixgram logo. - Everything runs on-device from realistic, deterministic sample data in one Swift file (for example Fixtures.swift: real-sounding names, handles, numbers, timestamps and captions). No backend, no login, no network calls except loading images, and no permissions (camera, photos, location, contacts, notifications, microphone). Do not persist state (no UserDefaults, @AppStorage, SwiftData or files): every launch starts from the same sample data, so the demo is repeatable. - Images: load images.unsplash.com photo URLs (with ?w=800&q=80 style parameters) with AsyncImage or a small cached image view and a tasteful placeholder. Check every image URL with check_urls before using it and replace any that does not answer 200. No broken or blank images anywhere. - Polish: native spacing and typography, safe areas, smooth spring animations (.spring or .snappy, most under 350 ms), matchedGeometryEffect for hero and expand/collapse transitions where it helps, .sensoryFeedback haptics on key taps, pressed states, and loading and empty states. Simulated waits stay under 3 s. Every visible button does something sensible; nothing is a dead end. - Keep the compiler happy: small files (under about 300 lines), big view bodies split into subviews, and no long chained expressions. - It must build with zero errors and run in the iOS simulator without a crash. Check the main flows on the simulator and fix anything broken.