A passion project inspired by a close friend diagnosed with Stage 3 Oligodendroglioma.
Dec. 2024 - Jan. 2025
Cancer patients experience immense stress before diagnosis, during treatment, and even after recovery. This stress can negatively impact treatment outcomes, potentially contributing to tumor growth and spread. Current apps address some user needs, but are not complete solutions.
How can we reframe the experience of cancer to make it more hopeful and positive to decrease stress for everyone involved?
Research published in British Medical Journal reported that approximately 20% and of cancer patients suffer from depression, and 10% and experience anxiety disorders.
20% suffer from depression.
10% experience anxiety disorders.
Journal of Clinical Oncology found that about 22% of cancer survivors present with lifetime cancer-related PTSD.
22% of cancer survivors present with PTSD.
According to the National Cancer Institute
To decrease stress, anxiety, and depression for cancer-diagnosed patients, I created an education, visualization, support app that helps patients and surrounding people understand and navigate a cancer diagnosis.
A study published in the Journal of Clinical Oncology found that patients who are well-informed about their cancer and treatment options experience 20-30% lower levels of anxiety and depression compared to those who feel uncertain about their care.
20-30% lower levels of anxiety and depression when informed about their cancer.
No more headaches when trying to access the most vital information.
Beacon allows you to sign up within seconds so you can access your personalized information as soon as possible.
Every form of cancer is built in so users don't feel isolated about their diagnosis.
Beacon makes sure every patient/person is seen. It delivers personalized content based on info inputted during onboarding.
No more ambiguity or having to look for the necessary information.
Beacon makes sure every patient/person is seen. It delivers personalized content based on info inputted during onboarding.
I first looked into the market to determine whether existing apps were effectively helping patients understand their cancer treatment plan and offering proper support. I dove deeper into Outcomes4me and ACS Cares, which are two of the most popular cancer support apps available currently.
It's evident that existing apps do have support resources and articles that inform users of their diagnosis. What's missing is the optimistic energy, personalization, and treatment visualization that breaks down the diagnosis into simpler terms. For my redesign, I wanted to focus on these key features.
Here is an example google search for the survival rate of Glioblastoma. When patients see the 6.9% 5-year survival rate, specifically younger patients, they may be discouraged, which can lead to worsening of symptoms, furthering depression or anxiety. Instead of focusing solely on survival rates or grim statistics, I aimed to emphasize positive words of affirmation, treatment options, support resources, and success stories.
My first instinct was to emphasize positivity throughout the app, but it's also important to note that some people don't want hope, but rather realistic news and how to prepare with the inevitable. People need support with coming to terms with death rather than staying strong and surviving. It's important to consider edge cases and think about designing for the entire audience.
For my design, I wanted to emphasize positivity but also leave an option for those who want to be more realistic.
People who have loved ones or close friends in cancer treatment need support as well. Here is some evidence from my research supporting this fact. People often struggle with finding ways to support the people who are experiencing cancer.
While testing out ACS CARES, the main app for cancer support, I noted the amount of time and clicks it took for a user to access the core features of the app.
12+ clicks just to access content.
5 minutes approximate time to onboard.
This was the home screen for ACS CARES app. I signed up as someone “having a loved one with brain cancer”. As a user, I want to learn more about the specific cancer without having to look everywhere for relevant info. Also, the cancer options were more generalized. Instead of having the option for Oligodendroglioma, it grouped all the brain cancers together in a tab called “brain and special cancers”. When creating a support app, personalization needs to be emphasized. Users want to make sure their diagnosis is seen.
Before designing, I researched how patients handle cancer diagnoses and the challenges they face with support apps. I interviewed my friend and analyzed data from Reddit threads to identify paint points, feature ideas, and user needs, which I organized into an affinity map.
Users need personalization, a community, and context to feel more in control about their situation. In my redesign, I aimed to tackle all of these points.
With user problems in mind, I brainstormed potential solutions, without considering feasibility at this stage.
After going through the ideas, I narrowed down the features I wanted to design. I decided not to implement the integration with apple health kit for now due to time constraints and lack of user needs.
Here were the 6 core features I looked to implement in my new design.
Personalized articles for cancer patients and surrounding patients
Treatment visualization to ease stress and provide context
Ability to save favorite articles, videos, or support groups
Users can watch success stories and persona anecdotes.
Support system for different groups.
Ability to volunteer and post success stories or videos to the app.
Users can access personalized content and suggested support groups in the home screen.
Users can view how their cancer treatment fights cancer.
Instead of making users sign up right away, I delayed the account creation until it was absolutely necessary to prevent friction and decrease drop offs.*progressive onboarding
I iterated upon my sketches and constructed these lo-fi prototypes to get some user feedback early in the process. If there was anything I needed to change, I could do so without having to sacrifice significant time or effort.
I tested my prototype with three users who were curious to learn more about different cancer treatments. All users liked the personalized articles and success stories that were introduced at the start. This was reassuring because these two functions were our primary focus, and what distinguishes us from existing apps.
While my ideal testing group would include real patients or people connected to patients, I recognized that accessing this group for testing at this stage would be challenging. Therefore, I decided to reserve testing with real patients for my high-fidelity interactive prototype, where their feedback will be most impactful.
Some users noted that the regulation of these in-app support groups may be difficult.
With this in mind, I decided to remove the support groups function and focus on providing users with professional help that is consistent and is known to help.
Support groups sound great in theory. What can go wrong for a safe space where patients can share struggles and help each other? The vulnerability of cancer patients, combined with the potential for misinformation or harmful interactions, makes it too risky to let users provide support to one another.
Established platforms like Reddit, with their strict moderation and regulatory practices, are better equipped to handle these complexities.
To ensure consistency and safety, it's best to focus the app on consistent resources for professional help. Established platforms like Reddit, with their strict moderation and regulatory practices, are better equipped to handle these complexities.
To be an effective, professional app that meets my visions, I want every type of cancer and treatment to have a support article and visualization graphic associated. In an ideal world, I would have every edge case documented on the app so users don't feel neglected or alone in their journey. For this app design, I simplified this scenario to tackle one form of cancer.
My goal of the Hi-Fi prototype is to validate if my design changes are genuine improvements, if people would use the app over other alternatives, and test the usability. I created a basic interactive prototype using Figma to test my hypothesis.
I moderated user testing with 5 users with varying backgrounds. One was my friend, current cancer patient. The rest included people who were interested in learning more about cancer.
Here's a brief overview of the process:
To quantitatively measure the success of the design, I broke down the larger design goals into detailed, measurable ones, and developed a questionnaire to help me answer those questions.
Alleviate stress and anxiety from users educational content
Allow users to explore personalized content
Help users understand more cancer treatment plans to decrease stress and uncertainty
Instill positivity and optimism through success stories
Q: How much did learning more about diagnosis decrease stress and anxiety levels?
Q: Does the personalized content increase your engagement?
Q: Did learning about different treatment plans help with clearing confusion or uncertainties
Q: Did you feel more optimistic reading and seeing the success stories right here in the app?
I was able to gather a lot of positive feedback on the prototype, each with varying backgrounds. Here’s a summary of the questionnaire.
Most importantly, none of my features had a negative effect on the 5 users tested. All users noted an improvement in their cancer support experience in one form or another.
The most significant outcome was the increased optimism users felt after seeing success stories. This makes sense, as users are often encouraged when they see someone in a similar situation improve.
60% of users reported no change in their feelings when learning more about their diagnosis, which is understandable given the neutral nature of facts. Proactive users may have also done their own research prior. After discussing with some users, many have noted that the first thing they would do is to search up their diagnosis on Google. It wouldn’t make sense for users to go straight to downloading the app.
I made sure to write down each piece of user feedback during testing. I used FigJam to organize and group the feedback by sections in the app.
Users noted that the onboarding process felt too interrogative and more like a survey. These were the changes I implemented below to address the issues.
Using an UX technique called progressive disclosure, I decreased the cognitive load for users through the separation of each question.
I added progress dots in the bottom to indicate how far along the user was in the onboarding process. Having a progress visual will motivate users to continue to finish their onboarding and reassure them of any uncertainties.
I added friendly language in the first screen to make the onboarding process feel less invasive, tedious, or negative. I wanted users to feel safe and supported when they first download the app.
Users introduced an edge case where they might not fully know the diagnosis. In this case, they want to be able to manually navigate to the diagnosis by narrowing down possible options.
Adding a manual lookup option enhances the app's usability by simplifying the process of finding a diagnosis. This feature is especially helpful for users who may not know their exact diagnosis or struggle to remember the spelling of complex medical terms.
Users noted that not everyone may be familiar with icon meanings, which can increase confusion in the app.
Adding descriptions ensures that people of all backgrounds, including varying ages, abilities, and needs, can navigate the app with clarity and ease. Universal design is especially critical for medical apps, as it promotes accessibility and inclusivity for all users.
Here's the latest prototype with some of my updated changes.
My app relies on existing data to deliver relevant content to each user. Adding an option for users to volunteer success stories or other useful information could help keep the app's content fresh and up-to-date. I initially excluded this feature from the MVP, as it requires an established user base to be effective.