2024
Scan & Order
Scan&Order is a UX-driven solution that simplifies food ordering for people with dietary restrictions. By generating a personalised QR code that filters menu options instantly, it reduces risk and uncertainty. Developed through user research, prototyping, and testing, the concept prioritises accessibility, safety, and seamless platform integration.
UX/UI
Branding
Concept
This project was made as a part of a university project and required me to design a solution based on a self-researched problem that is evident amongst digital ecosystems today; people today have trouble ordering food online due to various food allergies and restrictions. The answer to this problem comprised of user research, comparative analysis, prototyping and testing. The application I designed was a dietary filtering application which partners up with famous food delivery applications such as Uber Eats and Doordash. It also allows users to share their dietary information for combined ordering that allows for an optimal experience. Overall, this project challenged my critical thinking skills and allowed me to view the world of UX from a new angle,
Project Requirements
Timeline: 10 weeks
Project Type: UX/UI & Brand Design
Collaboration: Individual
Research
User Research
The user research was done carefully by making empathy maps after interviewing users. The user personas were carefully checked and improved for any errors found after the task was done. The empathy maps for both the applications, Ubereats and Doordash were analysed again to get a further understanding into the users mental model.
Ideation
Low - Fidelity Sketching
The ideation process was fairly short and was possible through the brainstorming that was done taking assessment one into regard. I was originally leaning towards making an extension of the Doordash application which would use an AI tool to detect past orders and suggest new places accordingly. However, I soon realised that doing this would just solve the problem for one application. This led me to brainstorm even more ideas and come up with an application that develops QR codes containing one's dietary requirements. When the code is scanned by another user, they would get filtered results according to both their dietary requirements.
Key Features + Prototyping
Sitemapping and Task-Flows…followed my prototyping
Key features of the application were identified and designed using a site map
Task Flow 1
Displaying the Doordash QR code on device.
Task Flow 1
Displaying the Doordash QR code on device.
Prototyping
For the prototyping, I mainly focused on the interactions that were going to take place (both major and minor interactions) while still focusing on the UI of the design. I wanted users to have good user experience and hence made sure to make my design straightforward and understandable. For example, in the image above, the wireframe I had created was performed using the wizard of oz method while they were doing the think aloud process helped me in developing the users mental model regarding this low fidelity prototype. I also kept Nielsen’s heuristics in mind after evaluating the feedback from task 1 and therefore incorporated many error prevention methods such as double checking with the users if either they wanted to delete or archive an application. The feedback I got from the users was carefully analysed and many components from the low fidelity prototype were improved.
Prototyping
For the prototyping, I mainly focused on the interactions that were going to take place (both major and minor interactions) while still focusing on the UI of the design. I wanted users to have good user experience and hence made sure to make my design straightforward and understandable. For example, in the image above, the wireframe I had created was performed using the wizard of oz method while they were doing the think aloud process helped me in developing the users mental model regarding this low fidelity prototype. I also kept Nielsen’s heuristics in mind after evaluating the feedback from task 1 and therefore incorporated many error prevention methods such as double checking with the users if either they wanted to delete or archive an application. The feedback I got from the users was carefully analysed and many components from the low fidelity prototype were improved.
Testing
The think aloud method from the users was recorded and then analysed thoroughly. The results were then carefully analysed according to each feature of the UI and supporting interactions.
Iterations
ITERATION 1 This iteration was developed on the Adobe XD software and roughly focused on the UI component of the application. I was pleased with the overall idea as it greatly resembled the paper prototype. However something was off (either the colour scheme or the overall layout of the application) so I sent this iteration to all three of my users for feedback. The feedback consisted of both negative and positive comments which included the colours, the compact layout and the prioritisation of some content.
Iterations
ITERATION 1 This iteration was developed on the Adobe XD software and roughly focused on the UI component of the application. I was pleased with the overall idea as it greatly resembled the paper prototype. However something was off (either the colour scheme or the overall layout of the application) so I sent this iteration to all three of my users for feedback. The feedback consisted of both negative and positive comments which included the colours, the compact layout and the prioritisation of some content.
Iteration 2
After understanding the feedback from Iteration 1, iteration 2 was formed and consisted of minor changes. For example, the applications were a bit more spread out from one another based upon the feedback received that the previous iteration looked a bit compacted. This iteration was sent to the users again for feedback and the main point received were; - It still looked a bit off in terms of the design - There were no cross options - Apps were not labeled
Iteration 2
After understanding the feedback from Iteration 1, iteration 2 was formed and consisted of minor changes. For example, the applications were a bit more spread out from one another based upon the feedback received that the previous iteration looked a bit compacted. This iteration was sent to the users again for feedback and the main point received were; - It still looked a bit off in terms of the design - There were no cross options - Apps were not labeled
Iteration 3
The final iteration that was developed was completely different in terms of the aesthetics. Looking at and understanding the user feedback from both the previous iterations it was decided to try something completely new. However it didn’t follow most of the apple guidelines and was therefore off-putting to users.
Iteration 3
The final iteration that was developed was completely different in terms of the aesthetics. Looking at and understanding the user feedback from both the previous iterations it was decided to try something completely new. However it didn’t follow most of the apple guidelines and was therefore off-putting to users.
More Works
(SL® — 02)
©2024
FAQ
01
What does a project look like?
03
Are all projects fixed scope?
05
How do I measure success?
06
What do I need to get started?
2024
Scan & Order
Scan&Order is a UX-driven solution that simplifies food ordering for people with dietary restrictions. By generating a personalised QR code that filters menu options instantly, it reduces risk and uncertainty. Developed through user research, prototyping, and testing, the concept prioritises accessibility, safety, and seamless platform integration.
UX/UI
Branding
Concept
This project was made as a part of a university project and required me to design a solution based on a self-researched problem that is evident amongst digital ecosystems today; people today have trouble ordering food online due to various food allergies and restrictions. The answer to this problem comprised of user research, comparative analysis, prototyping and testing. The application I designed was a dietary filtering application which partners up with famous food delivery applications such as Uber Eats and Doordash. It also allows users to share their dietary information for combined ordering that allows for an optimal experience. Overall, this project challenged my critical thinking skills and allowed me to view the world of UX from a new angle,
Project Requirements
Timeline: 10 weeks
Project Type: UX/UI & Brand Design
Collaboration: Individual
Research
User Research
The user research was done carefully by making empathy maps after interviewing users. The user personas were carefully checked and improved for any errors found after the task was done. The empathy maps for both the applications, Ubereats and Doordash were analysed again to get a further understanding into the users mental model.
Ideation
Low - Fidelity Sketching
The ideation process was fairly short and was possible through the brainstorming that was done taking assessment one into regard. I was originally leaning towards making an extension of the Doordash application which would use an AI tool to detect past orders and suggest new places accordingly. However, I soon realised that doing this would just solve the problem for one application. This led me to brainstorm even more ideas and come up with an application that develops QR codes containing one's dietary requirements. When the code is scanned by another user, they would get filtered results according to both their dietary requirements.
Key Features + Prototyping
Sitemapping and Task-Flows…followed my prototyping
Key features of the application were identified and designed using a site map
Task Flow 1
Displaying the Doordash QR code on device.
Prototyping
For the prototyping, I mainly focused on the interactions that were going to take place (both major and minor interactions) while still focusing on the UI of the design. I wanted users to have good user experience and hence made sure to make my design straightforward and understandable. For example, in the image above, the wireframe I had created was performed using the wizard of oz method while they were doing the think aloud process helped me in developing the users mental model regarding this low fidelity prototype. I also kept Nielsen’s heuristics in mind after evaluating the feedback from task 1 and therefore incorporated many error prevention methods such as double checking with the users if either they wanted to delete or archive an application. The feedback I got from the users was carefully analysed and many components from the low fidelity prototype were improved.
Testing
The think aloud method from the users was recorded and then analysed thoroughly. The results were then carefully analysed according to each feature of the UI and supporting interactions.
Iterations
ITERATION 1 This iteration was developed on the Adobe XD software and roughly focused on the UI component of the application. I was pleased with the overall idea as it greatly resembled the paper prototype. However something was off (either the colour scheme or the overall layout of the application) so I sent this iteration to all three of my users for feedback. The feedback consisted of both negative and positive comments which included the colours, the compact layout and the prioritisation of some content.
Iteration 2
After understanding the feedback from Iteration 1, iteration 2 was formed and consisted of minor changes. For example, the applications were a bit more spread out from one another based upon the feedback received that the previous iteration looked a bit compacted. This iteration was sent to the users again for feedback and the main point received were; - It still looked a bit off in terms of the design - There were no cross options - Apps were not labeled
Iteration 3
The final iteration that was developed was completely different in terms of the aesthetics. Looking at and understanding the user feedback from both the previous iterations it was decided to try something completely new. However it didn’t follow most of the apple guidelines and was therefore off-putting to users.
More Works
(SL® — 02)
©2024
FAQ
01
What does a project look like?
03
Are all projects fixed scope?
05
How do I measure success?
06
What do I need to get started?
2024
Scan & Order
Scan&Order is a UX-driven solution that simplifies food ordering for people with dietary restrictions. By generating a personalised QR code that filters menu options instantly, it reduces risk and uncertainty. Developed through user research, prototyping, and testing, the concept prioritises accessibility, safety, and seamless platform integration.
UX/UI
Branding
Concept
This project was made as a part of a university project and required me to design a solution based on a self-researched problem that is evident amongst digital ecosystems today; people today have trouble ordering food online due to various food allergies and restrictions. The answer to this problem comprised of user research, comparative analysis, prototyping and testing. The application I designed was a dietary filtering application which partners up with famous food delivery applications such as Uber Eats and Doordash. It also allows users to share their dietary information for combined ordering that allows for an optimal experience. Overall, this project challenged my critical thinking skills and allowed me to view the world of UX from a new angle,
Project Requirements
Timeline: 10 weeks
Project Type: UX/UI & Brand Design
Collaboration: Individual
Research
User Research
The user research was done carefully by making empathy maps after interviewing users. The user personas were carefully checked and improved for any errors found after the task was done. The empathy maps for both the applications, Ubereats and Doordash were analysed again to get a further understanding into the users mental model.
Ideation
Low - Fidelity Sketching
The ideation process was fairly short and was possible through the brainstorming that was done taking assessment one into regard. I was originally leaning towards making an extension of the Doordash application which would use an AI tool to detect past orders and suggest new places accordingly. However, I soon realised that doing this would just solve the problem for one application. This led me to brainstorm even more ideas and come up with an application that develops QR codes containing one's dietary requirements. When the code is scanned by another user, they would get filtered results according to both their dietary requirements.
Key Features + Prototyping
Sitemapping and Task-Flows…followed my prototyping
Key features of the application were identified and designed using a site map
Task Flow 1
Displaying the Doordash QR code on device.
Prototyping
For the prototyping, I mainly focused on the interactions that were going to take place (both major and minor interactions) while still focusing on the UI of the design. I wanted users to have good user experience and hence made sure to make my design straightforward and understandable. For example, in the image above, the wireframe I had created was performed using the wizard of oz method while they were doing the think aloud process helped me in developing the users mental model regarding this low fidelity prototype. I also kept Nielsen’s heuristics in mind after evaluating the feedback from task 1 and therefore incorporated many error prevention methods such as double checking with the users if either they wanted to delete or archive an application. The feedback I got from the users was carefully analysed and many components from the low fidelity prototype were improved.
Testing
The think aloud method from the users was recorded and then analysed thoroughly. The results were then carefully analysed according to each feature of the UI and supporting interactions.
Iterations
ITERATION 1 This iteration was developed on the Adobe XD software and roughly focused on the UI component of the application. I was pleased with the overall idea as it greatly resembled the paper prototype. However something was off (either the colour scheme or the overall layout of the application) so I sent this iteration to all three of my users for feedback. The feedback consisted of both negative and positive comments which included the colours, the compact layout and the prioritisation of some content.
Iteration 2
After understanding the feedback from Iteration 1, iteration 2 was formed and consisted of minor changes. For example, the applications were a bit more spread out from one another based upon the feedback received that the previous iteration looked a bit compacted. This iteration was sent to the users again for feedback and the main point received were; - It still looked a bit off in terms of the design - There were no cross options - Apps were not labeled
Iteration 3
The final iteration that was developed was completely different in terms of the aesthetics. Looking at and understanding the user feedback from both the previous iterations it was decided to try something completely new. However it didn’t follow most of the apple guidelines and was therefore off-putting to users.
More Works
©2024
FAQ
What does a project look like?
Are all projects fixed scope?
How do I measure success?
What do I need to get started?