iOS Health App

This design challenge is use for teaching purposes. The goal of the mini project is to show the process of UX and deliver a "potential idea" for grow daily active users in this app. 


Figure 1: Health App website (Apple 2021)


User Research


Main goal of this discovery was to understand who the user is.
What are their biggest struggles and where are the biggest opportunities to increase the app’s DAU?


10-20 minute interviews with iPhone users. There was no prioritization in gender or age. 

Screener questions

Do you have and use an iPhone?   Do you use iOS Health App?




User Journey

Top Insights

· Users that own an Apple Watch use the Health App more often, but only a few have an AW

· All users were interested in step tracking

· More than half were interested in sleeping

· They don’t seem to use many other types of data

· People have other smart watches like Samsung (Samsung Health) and Garmin (Garmin Connect) which are taking market share from iOS users

 · I found more female iPhone users than Male iPhone users

· 1 out of 3 women tracks her cycle in the Health App

· They mentioned that there is too much data, and they don’t know what to choose (Analysis Paralysis)


To have a better overview of the opportunities and pain points a User Journey helped me observe where are the most common struggles were.

Phrase the opportunities as “How Might We”, this to help trigger ideas and solutions

*This Journeys reflect a combination of different users that have common statements



Data Input

To understand what creates the most impactful solution, we would like to have some data, like... What is the % of users that visit the app on a daily, weekly, monthly basis?

· How many women use the Cycle information? How often do they open the app?

· How many users own an AW? if so, do they open the app more often? Is this the biggest opportunity space? What is the impact we are looking for? %.

· Is that metric connected to a bigger objective? For this particular project, I only estimated with rough user interview data.


Figure 2: Health App website (Apple 2021)



Re-framed opportunities (HMW). From this where one can start to think about different hypotheses that might help increase Daily Active Users. Rank them from most potential to least.



Ideation Session

Desk research

Checking other apps and how they have solved potential solutions for user engagement, helped me to understand what other solutions are out there that our users might already be using, like Garmin Connect and Samsung Health


There are different tools I use to spark ideas like Crazy 8’s. I like to check designkit methods for inspiration once in a while. Usually, collaboration here is a big plus, ideas can come from anyone.



Sketches and Wireframes

Draw several potential flows with different patterns in order to understand how they might play together. At this step, try to involve as many stakeholders as possible. Sparking conversation from different backgrounds is really insightful when it comes to choosing the potential ideas and the winning bet.

User Cases

There is always a happy path. However, understanding all edge cases helps designing with less potential blockers in mind and will speed the collaboration with Devs.





After thinking further on the potential ideas, I realized the one that convinced me the most was...

” Providing an on-boarding for users to set up goals and connect key metrics will give them a reason to check more often how they are doing”


User Testing

To check if the idea had potential, test the prototype with 2 people.


· What were the biggest questions about the flow?
· Did the users understand the steps?
· What do we need to improve?
· Which other expectations do they have?




Feedback Overview



Further Steps


The result from the user testing showed that there are many points that need further work. A couple more iterations on the design are needed.


Early feedback with developers and Product Owners to make sure we are constantly aligned is important.

Hand off

Make sure all assets and interaction specs are in the tickets.

This usually happens in Figma, Zeplin, XD and other similar software. It is good to know what can be done and what can not be done, or if it is too much effort.

Open questions

· Which edge cases do we have?
· What is the time frame?
· Can the data be minimized depending on the country? i.e. less american focus