CampusEats
A food-discovery and rating platform for Bennett University — built for the students who eat there, with magic-link authentication.
Case study
CampusEats
Problem
What gap does this fill?
Bennett University students had no structured way to rate or discover food outlets on campus. Recommendations happened informally through word-of-mouth, with no visibility into what was popular, what had improved, or what to avoid.
Solution
What was built
CampusEats is a Next.js 15 platform where Bennett students can browse food outlets, leave ratings across four dimensions (taste, value, service, hygiene), and read/write reviews. Authentication uses a magic-link flow restricted to Bennett University emails. An admin panel handles moderation and outlet management.
My Contribution
What I specifically built
I built the full platform — the Next.js frontend, Supabase backend, four-dimension rating system, the Bennett-email magic-link auth, and the admin moderation workflow.
Technology
Stack used
Frontend
Backend / Database
Auth
Engineering Decisions
Notable technical choices
Magic-link authentication restricted to @bennett.edu.in emails
ensures only real students can post reviews, maintaining authenticity without requiring manual verification.
Four-dimension rating system (taste, value, service, hygiene)
more useful signal than a single star rating, lets outlets understand specifically what to improve.
Supabase as backend
combines PostgreSQL, auth, and real-time subscriptions in one service, appropriate for a campus-scale product.
Admin moderation panel
gives outlet managers and admins the ability to flag/remove inappropriate reviews without exposing the raw database.