Roadmap

This is a rough list of the ideas I have for ZotMeal

Backend Changes:

• Make the backend fetch the menu a week in advance
• Separate the endpoints for the schedule and themed events data
• Improve the API status/testing page
  • add authentication so only admins can access it (nothing too complicated, maybe just a passcode + hashing that gets stored in cookies)
  • iframe showing the campusdish website alongside the API Response
  • interface to edit the cached menu
• Automated testing
  • on each release, with GitHub actions
  • periodic canary tests
  • clean up current error logging so I stop getting spammed by LogAlert
• Analytics
  • failure rate, number of requests
  • dashboard plus weekly email reports?
  • origin of requests
  • see what features users are actually looking at
  • Perhaps using Google Analytics?
• Research feasibility of deploying on UCI lab servers
• Better error messages
• Style and linting enforcement

Frontend Changes

• Display meals later in the day and for future days
• Finish and release android version
• Cache menu on the app
• Different colors/designs for different stations
• Push notifications or in-app popup for themed event days

Full-stack changes

• Email / text notification system for when your favorite foods show up on the menu
  • Web-based + in-app sign-up pages
  • integrated button in menu to sign up
• MyFitnessPal API integration
• Upvote/downvote feature
• Make a PWA version of the app