EatWhere
EatWhere is an fictitious app targeted to encourage locals to uncover the hidden gems of local food culture by exploring lesser-known hawker centres and food spots.
Design Process Pt.1: The Problem
As the want and pressure to eat fancy, aesthetic food grows with each generation, the current and younger generation are steering away from hawker centres to stay in the comfort of comfortable, fusion food in the form of cafes and restaurants.
This app aims to garner interests regarding domestic food tourism back into these groups of people.
Design Process Pt.2: Gathering Data
We conducted surveys and interview our intended target audience, getting their insights and experiences regarding the local food scene. From there, we analyse what are the targeted users' pain points by drawing up user personas and their journeys, and we came up with a lo-fi prototype to address those needs.
We also looked into competing apps to compare and reference to, and brainstorm how we could give our app an advantage over our competitors while successfully meeting the needs of our users.
To view our full documentation on this process, click here.
Design Process Pt.3: Task flows and Prototyping
After creating the lo-fi prototype, we conducted user testings with our users and made rounds of iterations in the form of mid-fi and hi-fi prototypes.
After we completed the high-fidelity prototype, we gathered some of our survey respondents and conducted usability testing with them to get feedback on EatWhere, such as if the app is intuitive, if it solves their pain points, and overall provides an engaging user experience.
To view our full documentation on this process, click here.
Role in the Team
In my team of 6, I helped out in the creation of the user personas and their flow, the prototyping for the final iteration of the EatWhere prototype, as well as conducting user testings user testings throughout the different iterations.
