NomNom Safe · Applied Software Engineering
Business application for allergen-aware menus
NomNom Safe treats menu data as living, safety-critical information. The business-side experience helps restaurants maintain explicit allergen signals, structured items, and trustworthy disclosures instead of informal free text alone.
Problem and users
Restaurants change ingredients, suppliers, and preparation steps often, yet allergen information is frequently scattered, implicit, or manually maintained without strong validation. NomNom Safe reframes the menu as a structured collection of items, explicit allergen signals, and contextual disclaimers so business users can review and publish safer data.
What I focused on
My recent sprint work concentrates on backend modernization, architecture, navigation, and responsive UI.
- Firebase migration: replace legacy MongoDB/Mongoose flows with Firebase Admin SDK operations, centralized Firestore services, and Zod-backed validation across API routes.
- Design principles: separate business logic from UI concerns, centralize API access, remove duplication, break down large components, standardize loading and error handling, and document the evolving architecture for contributors.
- Navigation: implement a consistent structure with clear entry points, breadcrumbs where helpful, accessible controls, preserved user state across routes, and responsive patterns such as mobile menus.
- Responsive design: fluid layouts, tuned typography and spacing per breakpoint, adaptive imagery/icons, and elimination of horizontal scroll on small screens while preserving accessibility.
Team context
Alongside platform engineering, the wider capstone team continues user research, prototyping, REST integration, and disciplined Scrum delivery. Parallel tracks cover MVP scoping, front-end refactors for business users, search and filter enhancements, and structured onboarding flows.