Fyrli - ADHD iOS app

Designing an iOS application for adults and parents

iOS app design • www.qbtech.com

Overview

Qbtech is the market-leading provider of objective ADHD tests for patients 6-60 years old. The tests are FDA-approved and CE-marked. For more than 20 years, Qbtech has provided objective tests for in-clinic use only by healthcare professionals (B2B). For the first time in the company's history, our design efforts are bringing these tests to people at home. We designed a native iOS application that includes their objective ADHD assessment designed by clinical psychologists as well as resources, a symptoms tracker, and collaborating clinics. The application is geared towards adults and parents.

Project details

Duration: 10 months
My role:
 Product designer
Team 1:
 1 designer, 1 product manager, 2 iOS developers, 1 back-end developer, 1 product owner, 1 test and verification engineer
Team 2: 2 iOS developers, 1 test and verification engineer
Tasks included:
Research, wireframes, prototyping, stakeholder management, roadmap shaping, high fidelity designs, design system, documentation

Outcomes

830
App downloads
120
Tests taken
~150€
cost savings/test
~40%
Lower waiting times

Why design the Fyrli app?

For the last 22 years of its lifetime, the company has been providing hardware (i.e. headband, motion-tracking camera, and laptop) to clinicians around the world to perform ADHD tests. The company had a few future goals:

  • The digitalization and modernization of their services. An iOS application would cater to these goals as well as reducing costs for hardware and maintenance in the process.
  • At the same time, the app would be reaching consumers at home instead of professionals in clinics which has been the case with the company's products so far. Having access to consumers' homes would create more visibility for the company as well as more revenue opportunities.
Image from https://www.suburbanbhs.com/services/qbtest-for-adhd

When did I come in?

When I joined the company, the project was in the discovery phase. I became part of a small design team alongside a lead designer and a junior designer. At that point, the lead designer had initiated research, conducting usability testing with 15 participants from the U.S. using an early prototype. I quickly got involved in the process.

After the research was completed, I worked closely with the lead designer to analyze the insights and shape the product direction. From there, I partnered with the product manager to define the product roadmap and led the design efforts for the app. Together, we identified and prioritized four key features to build the app from the ground up.

Wireframes

To focus on the functionality and involve the team as soon as possible, I started with wireframes and low-fidelity prototypes. This approach helped us focus more on the flow and content instead of the visual aspects of the app.

Wireframes - Starting screens of key flows
Wireframes - How a user would track their symptoms and mood on our app

Final designs and launch

Onboarding & key features

According to medical experts, ADHD is hereditary. Based on that fact, it was decided that the app should give to individuals a more personalised experience. From the start, in the app's onboarding, the user can choose to create multiple profiles (for themselves, their child or both). The finalised version of the app included four main features:

  • Take an ADHD test approved by medical experts
  • Track your ADHD symptoms as well as mood for the day
  • Read short articles and learn about ADHD
  • Clinic suggestions

Tracking ADHD symptoms & mood

One of the app's key features was offering the user a symptoms and mood tracker. By tracking their symptoms and mood daily, the user would create a journal that would help them recognise triggers and patterns of behavior associated with ADHD. They would also have the opportunity to share their journal with their doctor to aid with their diagnosis and treatment.

Design system

To ensure consistency across the application and establish a common language between us and the developers, our design lead and I created the app's design system from the ground up. I was responsible for maintaining it and introducing new components. Learning variables helped us set up the app's light and dark modes efficiently. We referenced the HIG (Human Interface Guidelines) at every step of the way, as we designed for iOS.

Design system - Tab bar menu component

Validation and Standard Operational Procedures

As part of the standard operational procedure dictated by the principles and methods of HFE (Human Factors Engineering) and user-centered design, I invited five users to validate the application's design. I was acting as the moderator. The five participants were assigned tasks guiding them to complete all the main flows in the app while sharing their comments and experiences with me. I documented and compiled their input in a formal validation report as directed by the relevant company's SOP document.

Results & Learnings

Designing and building the app concluded in 10 months and it was launched in Ireland. The purpose is to initially test it in Ireland as it is a smaller English-speaking target group. This will give us the opportunity to collect as much feedback as possible and continue with data-driven iterations. In 6 months time, we are planning to launch the new and improved app in the US market.

In compliance with my non-disclosure agreement, I've excluded and obscured confidential details in this case study. I am prohibited from sharing logos and anything related to the project until it has launched. All information presented is my own and may not necessarily align with the viewpoints of Qbtech. Any similarity to proprietary information is purely coincidental. Additionally, I do not own any copyrights of this brand, like the logo, imagery, or any related elements.

My workBack to topNext up: Payabl.