CampusHelper

Proof

• README documents authentication, uploads, search, claims, moderation, and database access controls.
• Source exposes API routes, validation, storage, and Prisma/Supabase data boundaries.

Problem

Campus lost-and-found posts need a searchable, authenticated flow where users can report items, add images, and find relevant matches.

Users and context

Built for campus communities that need a practical web flow for reporting and searching lost or found items.

Product workflow

Users sign in, create item reports with details and uploads, search existing posts, and review relevant lost-and-found entries.

Key engineering decisions

• Used authenticated flows so item reports can be tied to accountable user actions.
• Included uploads and full-text search to make reports easier to identify and retrieve.
• Kept reporting, uploads, search, and claims in one product flow instead of splitting the experience across separate tools.

Tradeoffs and limitations

• Adding uploads and search increases backend surface area compared with a static listing board.

Next improvements

• Improve moderation and matching flows for duplicate or related item reports.