Usability & Design & Functionality

 Usability & Design & Functionality Analysis

On week 2, we had a discussion post relating to the usability, design, functionality of an app from our choosing. I decided to choose one of the apps I use daily as go to navigation guide called Waze. Unlike other GPS applications, Waze takes a unique approach by relying on user-generated data to improve its navigation experience. This crowdsourced data allows users to contribute real-time information about traffic conditions, accidents, road closures, potholes, obstacles, and even animals on the road features that set Waze apart from other apps. For me, this real-time input from users is one of the main reasons I choose Waze over other GPS apps.


Usability

Upon startup, Waze allows users to quickly input their desired destination and begin their journey right away. The app also offers easy access to saved locations such as home, work, school, and other frequently visited addresses. Additionally, Waze tracks your travel patterns and, upon opening, provides personalized recommendations, making it even easier to reach your destination with just a tap—no need to type in an address or manually select from previously saved locations.






Usability Drawbacks

One of the drawbacks to Waze's usability is its traffic reporting feature. While I understand that the app relies on user feedback for accuracy, many Waze users will likely be driving alone without a passenger to assist with reporting. The current reporting process requires users to navigate through multiple layers of menus, which can be distracting and cause drivers to take their eyes off the road for several seconds. My suggestion is for Waze to implement voice commands for reporting traffic events, allowing users to report hazards hands-free rather than having to manually select options. For example, as shown in the screenshots below, after selecting the comment button on the main screen, users are prompted with a series of reporting options. If they select "hazard," they then have to choose the type of hazard, such as pothole, construction, or an object on the road. This multi-step process could be streamlined with voice commands to make reporting safer and more convenient for drivers.




Design

Waze adopts a minimalist design to clearly communicate traffic conditions and geographical data. The app uses color-coded routes to indicate traffic flow: red for heavy congestion, yellow for moderate traffic, and blue/purple for clear, uncongested paths and main path. On the main screen, a speedometer displays your current speed, and if the user exceeds the speed limit, the app highlights the current road’s speed limit and your speed in red, encouraging the user to slow down. The screen also shows your estimated arrival time and the remaining distance to your destination. At the top of the screen, the app provides the name of the current street and the distance remaining until the next street or exit you need to follow. One of my favorite features is the app's design for highway exits, which clearly shows you which lane to stay in. As seen in the screenshot below, all five possible lanes are displayed, but for your exit, Waze indicates that you should stay in the far-right lane, making navigation on busy highways much easier and more intuitive. Users also have a multitude of icons to choose from, representing potential events affecting the flow of traffic. 

Design drawbacks

One of the main design flaws in Waze is the clutter of icons that users encounter during their daily drives. Often, these icons don’t provide much value in terms of describing traffic flow or road conditions. As shown in the screenshot below, users are sometimes met with icons representing other Waze users. While the intent is to create a sense of community, this can detract from the app’s primary purpose—keeping the driver focused and aware of the road. The excess of icons can be distracting and interfere with the app’s core function of providing clear, essential navigation information. Waze also clutters the screen with icons for coffee shops, restaurants, gas stations, convenience stores, and more. While I understand that Waze may generate revenue from these icons, they often clutter the screen, no allowing the driver to digest the necessary information. These ads would be better suited for situations when the user is at a stoplight or during long stretches of highway driving where the focus on navigation is less intense. Displaying these icons during more critical moments of navigation only adds unnecessary distractions and detracts from the overall driving experience.


Functionality

Waze offers excellent functionality with real-time data that updates much faster than other navigation apps. I've consistently found that Waze provides quicker updates for road closures, accidents, and other events compared to Google Maps, Apple Maps, or integrated GPS systems. The app's integration with its community is a major advantage, allowing users to report incidents more quickly and accurately, making it a more reliable source of real-time information. I also appreciate how Waze generates multiple alternative routes based on user preferences, such as avoiding highways or tolls. Additionally, the app provides more detailed hazard alerts, enabling users to adjust their driving accordingly for a safer and more efficient journey.

Functionality Drawbacks

Some of the functionality drawbacks I've encountered with Waze include its performance when offline. While this is common for most GPS apps, many other apps can retain trip data and continue providing navigation as long as the route was set while the user had an internet connection. However, with Waze, if you're offline, you’ll lose your navigation path after about 5-10 minutes of driving because it doesn’t maintain the route data. Another issue is that Waze relies on user-generated data, which can sometimes lead to inaccuracies or delays in reporting. Since users must input data while driving, this can result in information being off by a few hundred feet or slightly delayed, impacting the app’s overall reliability.

Conclusion on the experience

Working through this discussion really helped me understand how an app should be built to be easy to use without messing with how it works. It should feel simple and natural to use, and the design should just make sense. What really sets it apart, though, is how well it works that’s what gets people to stick with it over other apps.

Comments

Popular posts from this blog

Programming Languages In The Role Of An Accountant

First Scratch Experience

Fundamental Concepts of Operating Systems