Application Design - Task 3: Low Fidelity Prototyping and Testing
21/11/2025 - 13/12/2025 (Week 9 - Week 12)
Shema Goldie Angwen / 0372129
Application Design I
Bachelor of Design (Hons) in Creative Media / Taylor's University
Task 3: Low Fidelity Prototyping and Testing
CONTENT LIST
INSTRUCTIONS
TASK PROGRESS
- WEEK 10-
- way finding: people don't need to think where to go but they are being guided
- signaletics: may find way anytime, anywhere. there is backup loop.
- the paradox of choice: less option make customers more certain what to choose
Then we did an exercise to differentiate global, supplemental, faceted, contextual, and local navigation. For this exercise, I chose Spotify as the example and analyzed how each navigation type is applied in its interface to guide users and organize content effectively.
This week, I started by finding references to better understand the direction of my design. I then created initial sketches and wireframes to plan the layout and user flow before moving to the lo-fi stage. After that, I moved on to the lo-fi prototype and began working on a few key pages to visualize the structure and interactions of the design.
Basically, this week I finished all the wireframes, completed them, and revised some inconsistencies.
Figure 1.1: Analyzing Spotify Interface
- WEEK 11-
From Mr. Sylvain's feedback, one key finding was the confusion between the “Depart Now” and “Later” options, which led to the decision to separate them into different pages to improve clarity and reduce user errors. I implemented this revision.
I also made additional changes, such as making the 'Accept' button more prominent and modifying the private ride and shared ride options so that only one can be selected at a time, whereas previously both could be clicked simultaneously.
- WEEK 12-
In this week, I finished all the prototype frames and conducted usability testing with 3 users.
Figure 2.1: Usability Testing #1
Figure 2.2.: Usability Testing #2
Figure 2.3: Usability Testing #3
Through the prototype testing, users were able to discover issues and insights that I had never thought would happened. Then, I continued revising the prototype, addressing the issues identified and improving the design based on the pain points that users had experienced.
ASSESSMENT
Link to Testing Recording Link: Click Here
Link to Canva: Click Here
Link to Figma: Click Here
FEEDBACK
WEEK 11: Separate the “Depart Now” and “Later” options into different pages.
WEEK 12: It got so much better, the layout is clean.
REFLECTION
Working on this ride-hailing app prototype has been a valuable learning experience. Starting from sketches and wireframes allowed me to explore layout and user flow freely, while creating a low-fidelity prototype helped visualize the “happy path” and identify potential usability issues early. Usability testing revealed important insights, I realized many problems won't be discovered if testing was not conducted. Making changes based on these observations reinforced the importance of testing and iterating designs to improve clarity and user experience. This process taught me how small adjustments, can significantly enhance usability. Moving forward, I aim to apply these lessons in the high-fidelity prototype, focusing on visual clarity, intuitive interactions, and a seamless ride-booking experience.
Comments
Post a Comment