This is a submission for the Built with Google Gemini: Writing Challenge
Every great project starts with a spark, and for the Community Home Meal Service, that spark was seeing students and workers struggling to find affordable, healthy food while local home cooks had no easy way to reach them.
What I Built with Google Gemini
I built a Community-Powered Meal Sharing Platform that digitizes the informal network of neighborhood home cooks. It provides a structured way for "providers" to share their menus and for "consumers" (like students or busy professionals) to find fresh meals nearby.
Demo
The Problem
In many neighborhoods, home-cooked meal services operate via messy WhatsApp groups or phone calls. There is no central place to browse menus, track order status, or verify providers. This makes it hard for new students or workers in an area to find reliable, affordable food.
What I Learned
Gemini played a crucial role in making this community-first application feel professional and intuitive:
Menu Architecture: I used Gemini to help structure the "Provider" and "Menu" data models, ensuring that the transition from a "User" to a "Meal Provider" was logically sound within the code.
Content Generation: Gemini assisted in creating realistic sample data for the providers and menus, which helped in testing the search and filtering functionalities.
UI/UX Guidance: I consulted Gemini to refine the "Clean and Modern" interface, helping me decide on the card-based layout and the flow for the Admin/User dashboards.
Demo
You can find the project source code and documentation here:
Community Home Meal Service GitHub Repository
https://github.com/ciriussaini/Meal-Service
Tech Highlights: This project is a robust prototype built with Vanilla HTML, CSS, and JavaScript. It uses LocalStorage for persistent data, meaning it works entirely offline and requires no complex backend setup to run!
What I Learned
Building a community-focused app taught me that the best tech is the tech that solves everyday problems.
Technical Skills: I mastered state management using LocalStorage. Handling role-based dashboards (Admin vs. User) without a traditional backend database was a fun and rewarding challenge.
Soft Skills (User-Centric Design): I learned to think from the perspective of a busy student. They don't want a complex app; they want to see "What's for dinner?" and "Is it approved?" in two clicks.
Unexpected Lesson: I realized how much a "Vanilla" stack can actually do. You don't always need a massive framework to create a meaningful community tool.
Google Gemini Feedback
The Good
Logic Troubleshooting: When I was stuck on the "Order Status Tracking" logic (Pending → Approved → Completed), Gemini was excellent at helping me visualize the flow and write the JavaScript functions to update the status in LocalStorage.
Creative Writing: It helped me write the "About Us" and "Community Guidelines" sections, striking the right balance between being professional and welcoming.
The Friction (The Candid Part)
CSS Nuance: Sometimes Gemini would suggest modern CSS properties that weren't the best fit for the "simple/clean" look I was going for, requiring me to manually trim back some of the extra styling.
LocalStorage Limitations: I tried to ask Gemini for advice on scaling, and while it gave good theoretical tips, it sometimes forgot the "No Backend" constraint I had set for this project.
Top comments (2)
Sagar, building this entirely without a backend using LocalStorage is super impressive. I totally relate to Gemini occasionally forgetting constraints and trying to overengineer things, keeping it focused on the vanilla stack must have been a fun challenge 😁
Thanks