top of page

WAVE System Design - App Structure and UI

WAVE Drowning Detection System is designed to provide a more reliable and safe swimming experience. It is an innovative real-time tracking system that uses lightweight wearables to determine if any swimmer is at risk of drowning. It immediately alerts your guards so they can investigate and intervene if necessary.



 

Information Archtecture

user stories, user flows, and navigations



Based on previous research, I started to think about what's the most important feature and result that we want from the user app. Below is the creative process. Other than the structure, we should be focusing on data visualization which could be the most direct interface to talk to users.


Main pages: MONITOR, MANAGE, SETTINGS






Question: Put it all in Settings? or Preferences ?

Besides the monitoring function we have, we need to manage Wearables and have access to change the WAVE System settings so that it could be a highly customized system and easy to use. In addition, to make it more user-friendly, we have functions like light/dark-mode and font size change. But how to group them?

  1. Option: Put all the settings in Settings

  2. Option: Separate in Settings and Preference

  3. Option: Separate in Settings and Preference and System

It is not possible to design for everyone.


And we can't just assume users will go to Settings page looking for color customize option. So we came up with a plan and decided to observe how users interact with it. Revise with feedbacks is the solution.





Design Sprints



Here are some rules I followed during the design and prototype:

  • Make actions reversible – be forgiving

  • Create an easy-to-navigate interface

  • Provide informative feedback

  • show the visibility of system status

  • Accommodate users with different skill levels



Reduce cognitive load


Cognitive load is the amount of mental processing power required to use a product. It’s better to avoid making users think/work too hard to use your product.

What I know is, this is going to be an ongoing process. After user testing or feature upgrade, I might get a totally unexpected answer. Challenging and full of possibilities, Iteration is the next step.


Comentarios


bottom of page