All projects

N9/02Web & appsComplexity: Light

Moodie-Foodie

Tell it your mood and budget; it picks the best-value meal from the campus canteens and today’s mess menu.

Status
Live
Year
2025
Built for
Google Developer Groups · IIITDM Kurnool
Languages
JavaScript, HTML
Team
Sujal Negi, Aryan Singh, Ashu Kumar
01

Overview

Moodie-Foodie answers the oldest question on campus: “what should I eat?” It is a mobile-first web app for the IIITDM Kurnool community that turns your mood, diet and budget into one clear suggestion from the canteens or the day’s mess schedule.

It runs entirely in the browser, with no server, so it opens instantly on a phone.

02

Problem and aim

Problem

Students waste time scrolling through several canteen menus and the mess timetable, often on a tight budget, before settling on something they did not really want.

Aim

Turn “what to eat?” into a quick, budget-aware decision that fits how you feel.

03

How it works

01 / 05

Your mood

Pick a mood (for example “Heavy” or something light), choose Veg, Non-veg or Both, and optionally set a price range or type a dish name.

02 / 05

Smart defaults

If you leave the price empty, the app sets a sensible budget for that mood (for a heavy meal, roughly ₹50 to ₹150) so you always get results.

03 / 05

Filter

suggestFood() filters every canteen item and today’s mess menu by mood, diet and budget. If you typed a dish, price limits are ignored so you can find it anywhere.

04 / 05

Rank by value

Substantial meals are preferred over snacks, and among them the cheapest one that matches your mood wins.

05 / 05

Two picks for “Both”

Choose Both and you get the best-value vegetarian and the best-value non-vegetarian option side by side, so neither is favoured.

04

Architecture

Everything runs in the browser

APage code/index.html

  • Input panelMood, Veg / Non-veg / Both, price range, dish name.
  • Result cardsBest picks, canteen call buttons, today’s mess menu.

BLogic code/logic.js

  • suggestFood()Validates input, filters, ranks and picks.
  • Price inferenceDefault budget per mood when none is given.
  • Mess menuFinds the current meal from the day and time.

CData code/data.js

  • Canteen itemsName, price, veg or non-veg, canteen.
  • Mess menuBreakfast, lunch, snacks, dinner for each day.
  • Canteen phonesTap-to-call links.

Request flow

  1. The page loads the menu data and the logic as plain script files. There is no server.
  2. You press “Get smart suggestions”. The inputs are read and checked.
  3. If you typed a dish, price limits are switched off; otherwise a sensible budget is filled in.
  4. Items are filtered, substantial meals are preferred, and the cheapest match for your mood is shown.
05

Languages and code

  • JavaScript63.5%
  • HTML36.5%

Repository

7 files980 linesTap any file to read its code

  • code/The app itself.
    • Every canteen item with its price and type, the full weekly mess menu and canteen phone numbers. 117 lines
    • Layout and styling (Tailwind CSS), the input form and the result area. 322 lines
    • The recommendation engine: price ranges, substantial-meal detection, food cards, suggestFood(), current-meal detection and the mess menu view. 424 lines
  • 11 lines
  • 21 lines
  • 50 lines
  • The decision flow written as a diagram: inputs → validation → dish override or price check → filter → rank → show. 35 lines
  • assets/The IIITDM Kurnool logo. on GitHub
06

Methodology

  1. Collect the canteen menus and the mess schedule into one dataset (data.js).
  2. Write the recommendation as clear, explainable rules rather than a black box.
  3. Design mobile-first, because students decide on their phones.
  4. Ship as a static single-page app so it loads instantly and costs nothing to host.
07

Technology

Front endSingle-page appNo server; everything runs in the browser.
Tailwind CSSResponsive, mobile-first layout.
Vanilla JavaScriptThe filtering and ranking logic.
HostingNetlifyFree static hosting with a public link.
08

Demo

09

Concepts

01What is a rule-based recommender?

A system that suggests items using explicit rules (filter by diet, then by budget, then prefer full meals) instead of a trained model. It is fast, predictable and easy to explain, which suits a small, well-understood menu.

02Why infer a default budget?

Empty filters often return nothing useful. A sensible default per mood means the user always sees a result, without having to fill in every field.

03What does “mobile-first” mean?

You design for the smallest screen first and add layout for bigger screens later. The result works well where most people actually use it.

10

Team