.h
product design · healthcare · novartis

ICan Care

Novartis cancer-support app: appointments, medication reminders, education, clinic listings, and research data collection. Built for patients, caregivers, and researchers.

UI/UX Designer Healthcare Mobile Novartis Privacy-first
Client
Novartis
cancer support
My Role
UI/UX Designer
end-to-end product UI
Platform
Hybrid mobile
iOS & Android
Tools
Adobe XD · Miro
ChatGPT · Flutter
Users
Patients & researchers
+ caregivers & clinicians
Domain
Healthcare
sensitive medical data

A hybrid app with
two jobs at once.

The brief was to create a hybrid mobile app that offered articles, reminders, and healthcare-provider listings, while also gathering user feedback for analytics and clinical research. Achieving that meant translating high-level requirements into specs that were usable for patients and secure enough for medical data.

Hero, pink ribbon, ICan Care wordmark, Novartis mobile application assets/icancare-hero.png
01 dual mandate

Support people. Feed research.

Patients needed appointments, medications, and trustworthy articles. Researchers needed anonymized data. The product had to serve both without making either feel like an afterthought.

02 sensitive data

Usability could not outrun security

Every flow (sign-up, reminders, surveys) had to handle medical information with encryption, clear consent, and privacy as a non-negotiable, not a settings toggle.

03 scale

Simple enough for daily use

The app needed to stay calm under a full feature set and remain usable for thousands of simultaneous users, not a dense clinical tool wearing a consumer skin.

Four outcomes,
one product.

With the constraints named, the work was aimed at four objectives that later became the information architecture.

01

Effortless schedules

Help people manage appointments and medications without hunting through calendars or paper lists.

02

Trustworthy content

Offer curated, accessible articles that raise awareness and support lifestyle, filterable by therapeutic area.

03

Research-ready data

Collect anonymized feedback and polls in a way that is useful for clinical studies without burdening the patient.

04

Security at scale

Design for encryption, privacy compliance, and thousands of concurrent sessions from the first screens, not a later audit.

Two audiences.
One privacy bar.

Stakeholder interviews, surveys, and contextual inquiry surfaced two primary groups. Both demanded clear reminders, simple navigation, and data privacy they could believe.

patients & caregivers

Manage treatment, stay informed

They needed help with treatment schedules and a way to find trustworthy information without wading through the open web.

clinicians & researchers

Anonymized signal, not extra work

They needed anonymized data for clinical studies and analysis, without compromising the patient’s experience or legal privacy requirements.

Keep the human
in every feature.

Two personas sat on the wall for the rest of the project. They shaped what we shipped and what we refused to complicate.

01 Hannah

Cancer survivor

Goals: stay informed about treatments and manage appointments. Pain points: forgetting medication times, and struggling to find information she could trust.

Persona. Hannah, cancer survivor assets/icancare-persona-hannah.png
02 Dr. Ravi

The researcher

Goals: analyze patient data to identify trends for clinical trials. Pain points: needing anonymized data while staying compliant with privacy law.

Persona. Dr. Ravi, researcher assets/icancare-persona-ravi.png

Four themes from
the research wall.

Affinity mapping turned findings into a strategy the rest of the screens had to obey.

personalization

Tailor the journey

Content and reminders follow each user’s medical path, not a generic broadcast.

transparency

Say what is true

Clear, trustworthy information about clinical trials and healthcare providers. No buried disclaimers.

security

Encrypt by default

Robust data encryption and privacy language in the product, not only in a policy PDF.

usability

Shorten the path

Simplify sign-up, reminders, and browsing articles until the daily loop feels obvious.

Home first.
Then the rest of life.

Navigation was iterated from user feedback. Home offered quick access to reminders, articles, and providers. Clinical trials and settings lived in their own sections so the daily path stayed uncluttered.

01 home

Greeting, awareness, today’s list.

A personalized home with an awareness banner, a weekly calendar strip, and today’s appointments and doses, plus polls when research needed a pulse.

Home dashboard, greeting, World Cancer Day banner, reminders assets/icancare-home.png
02 knowledge & safety

Specialists, interactions, honesty.

Provider messaging, a drug-interaction checker handoff, and an explicit educational disclaimer: the app informs; the treating physician decides.

Knowledge / centres, specialists banner, drug checker, disclaimer assets/icancare-knowledge.png

Sign up. Remind.
Read.

Critical workflows were defined before high-fidelity polish: registration, calendar-synced reminders, and content filtered by therapeutic area.

01 onboarding

Language, then an account.

Users pick a language, then create an account with name, email, and password, or continue with social login. The first screens had to feel calm, not clinical.

Onboarding, language select and create account assets/icancare-onboarding.png
02 reminders

How often, then when.

Add-medicine asks frequency, start and end dates, then lands on a calendar of doses and appointments that can sync with the phone calendar.

Reminders, add medicine frequency + calendar with doses assets/icancare-reminders.png

High fidelity on
both platforms.

Mid-fidelity sketches became interactive prototypes, tested on Android and iOS so usability issues showed up before engineering locked the structure.

01 centres

Find a hospital. See the details.

Search and city filters lead to centre cards, then a detail view with contact, address, social, and map, built for people who need a real place, not a brochure.

Centres, search list and centre detail assets/icancare-centres.png
02 menu

History, journal, privacy.

The menu holds medicine history, wellness journal, polls, tutorial, settings, and privacy policy, the slower, heavier tools kept off the home path.

Menu, profile, journal, polls, settings, privacy assets/icancare-menu.png

Iterate until the
task succeeds.

Three rounds of usability testing, plus a heuristic pass for error prevention, aesthetics, and efficiency. Navigation hierarchy and reminder setup were the biggest repairs.

findings

Hierarchy and setup

Navigation was hard to scan. Reminder setup felt long. Both were simplified before launch.

platforms

Android and iOS

Responsive behavior was checked on both so the hybrid shell did not hide platform-specific friction.

validation

92% task success

Final testing reached a 92% task success rate. Heuristics confirmed the remaining gaps were small.

+40%
Time on app
Engagement rose after launch as people used reminders and articles together.
85%
Schedules managed
Most users successfully managed appointments in the product.
+25%
Usable research data
Researchers reported a rise in usable data for clinical studies.
0
Reported breaches
Encryption and privacy constraints held through launch.
“The app makes it so easy to track my appointments and medications. The articles are also very informative and accessible.”
ICan Care user

What I’d carry forward.

Involve users before the screens harden.

Early interviews and three test rounds saved the information architecture. Waiting until high fidelity would have made the same findings expensive.

Privacy is a product requirement.

For medical data, encryption and anonymization are not a compliance appendix. They change what you ask, when you ask, and how you store the answer.

Two audiences need two speeds.

Patients live on home and reminders. Researchers live on polls and exports. Mixing those speeds on one screen helps neither.

Calm UI is a clinical choice.

Whitespace, short copy, and honest disclaimers are not decoration here. People open this app on hard days. The interface should not add weight.

This project reinforced that thoughtful design can change daily life, if you keep testing until the task, not the mockup, is the measure.

More Work