Hack, Reflect, Look Forward :: Google Gemini

Source: Dev.to

This is a submission for the Built with Google Gemini: Writing Challenge. 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.

The Problem

Gemini played a crucial role in making this community‑first application feel professional and intuitive:

• Menu Architecture: Used Gemini to structure the “Provider” and “Menu” data models, ensuring a logical transition from a “User” to a “Meal Provider” within the code.
• Content Generation: Gemini assisted in creating realistic sample data for providers and menus, which helped test the search and filtering functionalities.

Demo

GitHub Repository – Meal Service

Tech Highlights

• Built with Vanilla HTML, CSS, and JavaScript.
• Uses LocalStorage for persistent data, allowing the app to work entirely offline with no backend setup.

What I Learned

Technical Skills

• Mastered state management using LocalStorage.
• Implemented role‑based dashboards (Admin vs. User) without a traditional backend database.

Soft Skills (User‑Centric Design)

• Adopted the perspective of a busy student who wants a simple experience: “What’s for dinner?” and “Is it approved?” in just two clicks.

The Good

• Logic Troubleshooting: When stuck on the “Order Status Tracking” flow (Pending → Approved → Completed), Gemini helped visualize the process and write the JavaScript functions to update status in LocalStorage.
• Creative Writing: Gemini assisted in drafting the “About Us” and “Community Guidelines” sections, striking a balance between professionalism and friendliness.

The Friction (The Candid Part)

• CSS Nuance: Gemini sometimes suggested modern CSS properties that didn’t fit the desired simple/clean look, requiring manual trimming of extra styling.
• LocalStorage Limitations: Advice on scaling was useful, but Gemini occasionally overlooked the “No Backend” constraint of the project.