<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/7e07024d59e043a98dbd3dd8f28dcd38&quot; frameborder=&quot;0&quot; width=&quot;1658&quot; height=&quot;1243&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1243</height><width>1658</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1243</thumbnail_height><thumbnail_width>1658</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/7e07024d59e043a98dbd3dd8f28dcd38-57cef1aa353f11fd.gif</thumbnail_url><duration>389.483</duration><title>Campus Lost and Found Instagram-Style UX Case Study</title><description>This Loom demonstrates a campus lost and found portal UX and the key technical decisions behind it. Pratik shows browsing with lost and found filters, posting a lost item with details like type, color, category, and location (for example, Allies posting headphones at the 3rd floor library), and then another user submitting a claim and getting the poster notified for approval in MyItems before resolving. He explains choosing Supabase for authentication, database, and storage with row-level security, and selecting manual claim approval over automated matching to avoid false positives. He also lists future gaps including SendGrid email notifications and a fake post reporting and admin moderation queue, plus perceptual hashing image matching and in app messaging for privacy.</description></oembed>