U might be wondering what I was doing for this 1 month or so...
And the answer is that I was working very hard to develop the prototype.
After many sleepless nights, I would confidently say I am 80% done. YAYYY!!!
(FYI, 80% is actually A LOT ALREADY seriously speaking...)
But before I explain how I did it, I will share some images of the prototype.
Stall User Interface #1
Before a customer can even browse the web application, the stall owner have to first create a stall and a menu.
Customer User Interface #1
Afterwards, customers can browse the various stores in the food court.
The layout might look a bit weird, because there is only 1 stall, but it wouldn't if there's more.
Perhaps, what made the project so huge, is that I have to make it responsive as well. Most of the time, people would be using their phones to order instead of a laptop. Hence, the screen as well as user interface has to be modified to cater to devices of various screen sizes.
After ordering the food, users, can check their order history to view current orders and past orders.
The food ordered is "Fish & Chips",
from the Western Stall.
The status shown is "Requested".
If the stalls haven't accept their order yet, users can still cancel their food order.
Stall User Interface #2
After the customer has placed their order, it would be reflected on a simple order dashboard.
Here we can see that an order for "Fish & Chips" have been ordered.
The stall can either accept the order, or reject the order.
Let's assume the stall owner accepts the order.
The change would be reflected as shown.
Intuitively, if the stall accept the order, it will be shifted to the 'Completed Orders' Section.
However, what if the stall declines?
For "Incoming" and "Accepted" Orders, the order will be immediately rejected or cancelled if the stall declines. (Of course, there would be a confirmation button)
For "Completed" Orders, the order will instead be shifted back to the "Accepted" Orders. Why? Just in case order was accidentally being pressed as completed. However, it doesn't make sense for "Accepted" Orders, if declined, to be shifted back to "Incoming Orders" because, in that case, it might as well, be rejected.
Nevertheless, it's okay if it is not understandable.
Customer User Interface #2
Once the order has been accepted, the user would see the updated changes.
Status has been changed to "Accepted" and it is not possible to cancel the food order anymore.
Of course it would be a tedious job if one needs to keep looking at the phone to check if his order has been accepted.
Hence, the web application would send a notification to the user if there's any changes to the food order.
Once the food order is ready, the customer can collect his food at the stalls and enjoy their meal.
And that's all for this 1 month web application!
The next post would probably be focusing more on the back-end development as well as the whole development process.
So stay tuned!
댓글