Screenshot 2024-03-22 at 1.36.25 PM.png

Medical Vendor App

Medical Vendor App

Improving the usability of the SEC3URE mobile app by refining the navigation, integrating Bluetooth pairing to e-badge, and modernizing the interface.

Timeline
5 months
(SEP 2022 - JAN 2023)

Role
UX Designer

Cross Functional Partners
Product Management, Development


How can we improve the usability of this app while maintaining functional parity?


Context

The SEC3URE app allows Medical Vendors to upload credential documents, check-in to healthcare facilities, and transmit their check-in status to an e-badge via Bluetooth.

Due to developmental limitations, these functions were divided among two apps for 3 years. When the resources became available to merge the apps together, we aimed to modernize the interface design, improve usability, and maintain functional parity.

Process

  • Capturing the existing apps to ensure functional parity.

  • Whiteboarding, sketching, discussing how to tackle this project within the UX team.

  • Identify fonts, styles, and components that will make up the native app.

  • Creating and prototyping the final designs for the native app.

  • This project helped me establish an effective channel for communicating design discrepancies with our Product Owner. It also taught me that a the aesthetics and usability hold little value if the app is glitchy and unreliable.

Sneak Peek

Before

The home screen lacks an effective call to action and does not meet WCAG 2.0 accessibility standards.

The navigation items are not visible to the user, which inadvertently increases their cognitive load.

After

The home screen now features a large Check In button - the most frequently used function of the app. We adjusted the UI to create heavier contrast.

In addition to the hamburger menu, a bottom navigation bar with redundant items was added for quick, easy access.


Audit of existing app

The goal of the project was to re-design the app with feature parity. To ensure that all features were covered, I created a sitemap of screenshots in Lucid Chart. In doing this, I found these areas for improvement:

  • The navigation was hidden in a hamburger menu and contained 21 items, which is triple the amount of information a person can process at a time according to Miller’s Law.

  • The user had to dig through several screens before engaging with the app’s core functions, preventing them from quickly and easily completing their desired task.

  • Scheduling screens were not implemented, so users saw a blank, unresponsive screen after selecting any page in the schedule section. This lack of information was frustrating and confusing.


Ideation

Once we had a grasp on all of the existing app’s features, the UX team got together and brainstormed ways to make small but impactful improvements to the user experience.

The largest hinderance to usability of the original app was the way that the navigation was organized. By hiding all navigation behind a hamburger menu, users are forced to recall instead of recognize, which is warned against in Jakob Nielsen’s 6th Usability Heuristic.


Creating the Design System

To maintain visual and functional consistency across the app, we customized elements from the Material Design 2 component library. This creates a better user experience because the app will not only look more polished, but will give the user an expectation of what might be on any given page. This is also a better experience for the development team because re-using components saves the time and energy of coding bespoke components.


Final Designs

After countless meetings and iterations based on internal feedback from the Product Owner and Development teams, the final designs were complete. I created a functional prototype of the final designs of the app in Figma.

Click to see the interactive prototype


Reflection

Design QA

Prior to this project, there wasn’t a system in place to ensure that a product’s implementation accurately reflected the designs. To be proactive about this issue, I reviewed the pre-released implementations for inconsistencies, big or small. I created a Design QA document with quick blurbs and images explaining discrepancies I noticed between the intended design and what was developed. I shared this living, breathing document with the Product Owner, who used it as a reference point when creating JIRA stories. Later, I was told that this document was instrumental in creating small stories that could easily fill sprint gaps.

SIMPLICITY IS KEY

The objective of this project was to modernize the legacy app and increase usability, so I spent a lot of time pruning the navigation and designing a framework that would work across several different functions. Despite these cosmetic upgrades, reviews continue to echo the same message: The app is glitchy, slow, and unreliable. In hindsight, I wish I had advocated for a simplified version of this app that allowed users to perform two key functions: checking in and out of hospitals and transmitting information to their e-badge. This approach would have freed up resources to ensure that the app is fast and reliable for users, all of whom require access to the app in order to do their jobs.


Next Case Study

Form Automation

INTELLICENTRICS, FEBRUARY - APRIL 2023

Designing the interface that will allow AI to perform data-entry for doctors.