|
|
|
|
|
by wanderboy
5823 days ago
|
|
This is well-done. I'm working on a similar project, and one thing I'd like to point out is that menus are not always simple databases. There are several menus that have paragraphs of information that relates to several menu items rather than just one. How are you planning on translating that information to a mobile application, if at all? I'm trying to find a good example of this "paragraph of extraneous info" from menus in a Google Search - I'll get back to you when I can. |
|
In my experience, most restaurant menus do fit into a simple database format. After all, most major point of sale systems do use relational databases to store and track menu items. The menu item databases are usually highly configurable but I've usually seen them break down into:
1) Major categories: Entrees, Appetizers 2) Menu items: Cheeseburger, Grilled Salmon 3) Modifier categories: Steak Temperature, Salad Dressing 4) Modifiers: Rare, Medium, Well-Done, etc.
Of course you usually don't display the modifiers on the menu itself, that is a back end implementation detail. :)