HealthHub All projects

What matters today

Product design / asky

Health readings and everyday commitments compete for attention on the same screen. For HealthHub, I designed a personal overview that preserves numerical context and reorders its mobile layout around the day ahead.

Explore the screens
Prototype interfaceHealthHub
Room to compare
Demo dataHealthHub / Product design
Who it serves
People reviewing personal health indicators, activity and scheduled health-related commitments.
My role
Visual identity and user interface design.
Scope of this case
One personal dashboard in desktop and mobile layouts, using static demonstration values.

Between readings and routines

The dashboard combines readings with daily commitments. Four cards show health values and trends, weekly activity adds perspective, and the calendar identifies a selected date. Medication and consultations use distinct cards.

Desktop accommodates activity beside the calendar. A phone makes this composition sequential, so block order determines which question comes first. Prioritising the calendar is a design hypothesis that needs user testing.

Scenario logic

  1. 01

    Mobile reading order: four health indicators

  2. 02

    Selected date and calendar context

  3. 03

    Medication and consultation cards

  4. 04

    Weekly activity for comparison

What shapes the interface

01

Give each number context

A large value without its unit or direction of change leaves the reader to reconstruct its meaning.

Decision

Each of the four health cards combines a value, unit and trend. The weekly activity chart includes an average line as a visible reference for individual days.

Trade-off

A trend or average cannot explain why a reading changed. The overview does not provide grounds for a medical conclusion.

02

Reorder rather than compress

Simply stacking the desktop layout would place the calendar after activity and delay access to the selected day’s context.

Decision

Desktop places activity beside the calendar below the metrics. Mobile uses a 2 × 2 metric grid, moves the calendar before activity and introduces bottom navigation.

Trade-off

The weekly overview sits further down the phone page. People primarily checking activity may need more scrolling, which future testing should examine.

03

Distinguish daily commitments

Medication and a consultation call for different interpretations; identical event cards would obscure that distinction.

Decision

Separate card types distinguish medication from consultations. A selected state in the calendar provides a visible date reference while reviewing the page.

Trade-off

Selecting a date only changes its highlight in the demo. Updating events and handling dates without events remain implementation tasks.

A shared visual language

The palette and principles represented in the prototype. A full component specification is not yet part of this case.

01 / Palette

A personal visual language

Pink #F5C9F3, green #179A55, yellow #FFE985 and blue #416DE2 distinguish blocks. Labels carry the meaning of health information.

#F5C9F3
#179A55
#FFE985
#416DE2
02 / Principle

A stable card structure

Name, value, unit and trend retain their roles across layouts, preserving the elements needed to interpret each number.

03 / Principle

Adaptation through priority

The same blocks take different arrangements. Mobile prioritises the calendar while retaining the weekly perspective further down.

The decisions, in detail

Read-only HTML previews of the original Russian-language prototypes. Demo data; personal identifiers replaced.

Room to compareExplore the screen
01

Room to compare

Four indicators sit above the weekly chart and calendar, placing activity beside daily commitments.

The day before the weekExplore the screen
02

The day before the week

Units and trends remain within cards; the calendar precedes activity above bottom navigation.

What took shape

The responsive dashboard includes four indicators, weekly activity with an average, a calendar and differentiated event cards. Its mobile layout implements a different order for the calendar and activity blocks.

4Health cards with units and trends
2Responsive dashboard layouts
2Event types: medication and consultations

What to test next

01

Test scenario

In a future test, identify a reading’s value, unit and trend direction.

What to observe

Record unit errors, misread trends and cases where the average is mistaken for a personal normal range.

02

Test scenario

Find medication and a consultation on mobile, then locate the weekly overview.

What to observe

Observe search order, scrolling, backtracking and errors distinguishing event types.

03

Test scenario

After connecting event data, select a date and explain which commitments belong to it.

What to observe

Check date-to-card correspondence and understanding of an empty day without moderator prompts.

Next case study

Drillo

The current rental comes first

Original size. Scroll the screen to explore the details.

Open prototype separately ↗