I hope you are all doing well in these turbulent times.
I’m currently creating an app for my University Cafeteria that would allow them to publish the food that they are going to be serving on a daily basis. As this food changes daily, the Cafeteria wants to be able to publish details about the food.
This app would be used by students to order their food, where they would be able to pay, place the order, and receive live feedback (i.e. their phone buzzes) on when their food is ready.
Now, how would you guys think that I could create a platform for both of these users? I.e. give the cafeteria folks the ability to publish the food and see statistics, while giving the students the ability to rate the food, pay, and interact with the status of the food. These are linked by the same database, but I’m looking to give them two different user interfaces.
Any guidelines or links for this topic would be very much appreciated!
add a role field to datatype user (admin / student)
Add a admin button/link to dashboard in header, make it visible only for logged in users with “admin” role.
On dashboards page load workflow - if user is not logged in or admin redirect back to login popup.
In general I think it is always good methodology that administrators enters the same view users use daily - gives better quality in presentation.
You can also easily let the first admin add and remove other admin accounts.
I prefer individual accounts, make apps more personal and interesting for future development, but what you ask for can of course be achieved in many ways, also with less logic.
