Food Hunger App Design Report: UI/UX and Heuristic Evaluation

Desklib provides past papers and solved assignments for students. This report analyzes a food ordering app's design.

ASSESSMENT 5: REFLECTION on Food Hunger app
Student Name: Aswaraj
Student id: 11615096
1

Abstract
The target here to be achieved is to make a full report on the designing that has been done for
the given project, including the user interface and experience detailing a user might find in it
and justify that this is what a user would look for in the food ordering application.
The designing is done by keeping the heuristics principles in mind which covers all the
important aspects needed in a well-groomed application. Images, icons, clear navigations,
error messages, status of the system are some of the checkpoints which are reached in the
application.
And at last, the designing is completed successfully with all the user requirements being met,
by keeping in mind that a user won’t have to worry about using the application or face any
issue using it.
Introduction
The project aims at creating a design of the required restaurant for customers to log in or
register or continue without that too. With all the complete information and attributes an e-
commerce food website should have including cart, addition of items into cart, payment
modes, OTP for secure payment gateway, and other facilities which are needed. The
application is based on heuristic principles which are there to be followed while designing
such projects.
There is one project named “Food Phone Application” which shows the basics of food
ordering application (e.g., button size and text size) or usage of list view, which have been
adapted here. (Li, 2010)
Another similar work is seen in a project from where the designing part is taken into
consideration, such as: the top part of the application should not be much larger or addition of
discounts and offers. (Vitaly Dulenko, 2018)
Reflection of the designs of the interface
a. UI design:
The design is created while keeping the heuristics principles in mind. The 10 principles
depicted in that are implemented as follows:
 Visibility of the status – A user can see if the food is being prepared and how much
time it is going to take to get it prepared. (Figure: 1) (“The 6 Principles Of Design, a
la Donald Norman | Enginess Insights,” 2014)
 System’s relation to real world – the usual terminologies used in the application are
spoken and understood by all, for example everyone is aware that OTP stands for One
Time Password.
 Ease of controlling for user – the user can easily go back a page by clicking the back
button provided and even exit the application whenever he needs to.
 Prevention of error – if someone puts wrong credentials of their card, OTP an error
message will pop up and there are various confirmations which the app asks for.
(Figure: 2)
 Error recovery – if some error pops up they’re put in plain language without codes.
 Standards and Consistency – the icons used are known to everyone, for example the
turn off icon is there to close the app.
2

 Less recalling – users do not need to remember each and every aspect of the app,
there are options, and suggestions everywhere. For e.g. in login page your last entered
name would be suggested.
 Flexibility – there are directions provided for different links, for e.g., user can easily
switch between menu entries using links for those.
 Minimalist design – no useless attributes are put in the application, only those which
are of use are there and that too in a compact yet understandable way.
 Help – A user can also take help at any time from the service team sitting at backend
if they have any issue. (Figure: 3) (“10 Heuristic Principles – Jakob Nielsen’s
(Usability Heuristics),” 2005)
b. User requirements being met
 Starting the order by putting name and table serial - The customer can enter his name and
the table he is sitting at and proceed.
 Food menu – the food menu is there right after clicking the proceed button. The menu has
categories: Starters; Main Course; Desserts and Soft Drinks.
 Selection of desired food items – A user can just open the food list and select the item
he/she wishes to try and add them in the cart easily.
 Viewing individual food articles – As mentioned above individual food items can be
viewed easily just by clicking over them from the food list.
 Ordering food – There’s a button to confirms if the customer is sure about adding it to cart, on
proceeding, the food item is added to the cart.
 Order editing, and confirming – the cart is when added with food items it can be further edited,
by adding/removing items quantity, and then confirming the order.
 Payment – the payment page will open on clicking over GO TO PAYMENT button in the
above screen. Customer can choose debit or credit card to pay for the food by putting his/her
credentials.
 Order status – order status is added to display waiting time, and where’s the order currently, on
payment step or is being prepared.
 Registration – a customer can register himself after ordering food too. The details can be filled
in easily or can register using Facebook or Google account.
 Discounts, and offers – Links have been provided where a user can see if the restaurant has put
any discounts or offers on a selected food item.
c. The factors behind the design
 The user requirement played a major role in deciding what is to be put into the application and
what should not be. The requirement of putting a name and table’s number without having to
login or register first is one such aspect which was important to keep in mind while designing
as usually the login and/or registration is the first step in any ordering application.
 Putting the registration page after ordering food was one challenge, and adding offers,
discounts, and credit cards, the debit cards are usually expected to be put in such projects.
 The requirements were fulfilled by utilising the heuristic principles. Some of them are depicted
below:
 The visibility of the system status
 The prevention of errors
 The user controls
 The basic terminologies and words
3

 The common standards of understanding icons by recognising them easily were some of
the attributes which were kept in mind while designing according to the requirements
given.
 The last page was added in order to provide the users with all kinds of help he or she may
need.
d. A look at similar interfaces
The FEAST site which has been taken as a source for motivation and guidance here has provided a
lot of ideas on how the application should be.
 Similarities
 The main home page screen of the app depicts the basic links to be navigated at such as: home,
Signup, and other options (Figure: 4)
 The list view is there to show the various items
 The details of each food item are provided too.
 There are sections such as desserts, drinks which are also taken in our application. (Figure: 5)
(“Feast”, 2019)
 Differences - Other than that a few more features have been added to the application which brings
the edge over the FEAST site. Those features are:
 FEAST is more like a food delivery site.
 The delivery time provided in the FEAST is not quite answerable like it is in Food Hunger
application.
 The application provides details of the order including its waiting time which can be
confirmed to the staff right away too.
 Entering the restaurant one can only put up his table number and proceed for ordering food
without any registration or login requirement.
 On FEAST one cannot view individual food items too.
Conclusion
Hence, the application made here is fulfilling all the details and requirements with a structure so
easy to use and handle that a user won’t even need to opt for help option provided but still if he or
she does there’s that option. One can easily order food after a hectic time he or she might have had
without even signing in the application which one of the amazing features of this app. Individually
viewing food items, read its details and selecting the number of that items are other beneficial
aspects of the app, and the interface is quite user friendly and easy to operate. Therefore, it can be
said that the designing is done up-to the mark and does follow all the necessary instructions.
4

References
 Li, S. (2010). Food Phone Application A Project Presented to. Retrieved from
http://www.cs.sjsu.edu/faculty/pollett/masters/Semesters/Fall09/shengyu/
CS298%20Paper.pdf
 Vitaly Dulenko. (2018, June 19). UI/UX Case Study for the Restaurant App.
Retrieved from https://uxplanet.org/ui-ux-case-study-for-the-restaurant-app-
6657f033922f
 The 6 Principles Of Design, a la Donald Norman | Enginess Insights. (2014, January
1). Retrieved from https://enginess.io/insights/6-principles-design-la-donald-norman
 10 Heuristic Principles – Jakob Nielsen’s (Usability Heuristics). (2005, January 1).
Retrieved from http://www.uxness.in/2015/02/10-heuristic-principles-jakob-
nielsens.html
 Feast (2019). Retrieved from https://www.feasthq.com/
5

Figures
Figure 1: Order status
Figure 2: Alert messages example
6

Figure 3: Page for help
Figure 4: Main page option’s inspiration from Feast
7

Figure 5: Inspiration for various sections
8