{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/7e07024d59e043a98dbd3dd8f28dcd38\" frameborder=\"0\" width=\"1658\" height=\"1243\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1243,"width":1658,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1243,"thumbnail_width":1658,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/7e07024d59e043a98dbd3dd8f28dcd38-57cef1aa353f11fd.gif","duration":389.483,"title":"Campus Lost and Found Instagram-Style UX Case Study","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."}