Lostopedia

• 

  dashboard!

Inspiration

Lost my water bottle twice in the campus but still havent recovered it to this day. The lost and found section in my school's admin office was barely operational. Finding it on social media is like impossible cuz not everyone cares. Spamming whatsapp groups is the most viable option after all, but the process is manual and repetitive. And gets flooded by group chats.

What it does

Lostopedia is a unified lost and found platform for campus members. It allows students and staffs to post lost and found items in the campus. The app provides an ai-enabled (semantic similarity search) feature to match lost items to found items. The goal was to reduce the wastage and environmental impact of buying new items when it could've been recovered with a more efficient lost and found system.

How we built it

• DevOps: Vercel (for final deployment), Cursor IDE, Claude agents (opus + sonnet 4.5) HEAVY USAGE LOL, coderabbit for code reviews, byterover for context retention and saving memory of coding practices.
• UI: Mobbin for UI inspirations, shadcn and lucidreact icons A LOT.
• Stack: Next.js with api routes, Supabase as backend (auth, db, storage, edge functions)

Challenges we ran into

Build errors, linting issues. Thank god coderabbit caught that. Byterover saved us tons of time from reprompting instructions that've been used in the past. (noticed increase in dev speed fr)

Accomplishments that we're proud of

Deployed and shipped a fully functional production ready web app in less than 24hr.

What we learned

Planning things early is CRUCIAL. Man, we're legit rushing through our submission at t = 2 hours left.

What's next for Lostopedia

Rollout to TARUMT. Going for B2B institutional SaaS. Charge campuses an annual licensing fee based on student population. Make it Free of charge for students to use.

Built With

• byterover
• claude
• coderabbit
• cursor
• huggingface
• next.js
• postgresql
• supabase