asky.design

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
HealthHub / Prototype interfaceHTML prototype
Room to compare
Demo dataHealthHub / Product design
Who it serves
Insured people following a care plan set by a doctor: medication, appointments and regular measurements.
My role
Visual identity and user interface design.
Scope of this case
One personal dashboard in desktop and mobile layouts, using static demonstration values; the desktop layout is an authorial extension of the mobile cabinet.

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.

In the source system the cabinet receives a care plan from the doctor: medication, an appointment and measurements with their frequency, next to a measurement diary, questionnaires and articles. The prototype represents this with medication and consultation cards, a calendar and a plan for the day; weekly activity is an authorial extension beyond the original.

The case is based on a real public health insurance system (2023) covering both the insured person’s cabinet and the professional contour. The HealthHub name, identity and demonstration data are changed for publication, and the screens remain a prototype. The professional contour of the same system is shown in the LensCare case.

Scope of this case

One personal dashboard in desktop and mobile layouts, using static demonstration values; the desktop layout is an authorial extension of the mobile cabinet.

01

Give each number context

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

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.

03

Distinguish daily commitments

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

From the challenge
to the decision.

Design challengesChallenge
01

Give each number context

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

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.

03

Distinguish daily commitments

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

HealthHub / Prototype interfaceDemo data
01

Give each number context

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.

Prototype interface: Give each number context
Demo data
02

Reorder rather than compress

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.

Prototype interface: Reorder rather than compress
Demo data
03

Distinguish daily commitments

Separate card types distinguish medication from consultations; in the source care plan these are different events with different frequency. 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.

Prototype interface: Distinguish daily commitments
Demo data

Fragments of the current Russian-language prototype. The original interface for an evidence-based before/after comparison has not been added.

To add: the original screen, date and comparison conditions.

A shared language.
Down to the details.

The palette, component fragments and CSS values from the current prototype. The full system specification and usage rules still need to be added.

Colour / semantics

A personal visual language

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

01#F5C9F3
02#179A55
03#FFE985
04#416DE2
HealthHubPrototype interface
Typography / hierarchy
Aa123

Outfit

The family declared in CSS. Missing fonts or glyphs use the system fallback.

400500600700
11 / 13 / 18 / 29 px

To add: text roles and the complete type scale.

Components / states

Give each number context

Components / states: Give each number context
A fragment of the original prototype. Other states still need to be added.
Geometry / rhythm

Values from the layouts

Selected spacing and corner-radius values from CSS. These examples are not an approved token scale.

7101520
8913

The decisions, in detail

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.

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

Original size. Scroll the screen to explore the details.

Open prototype separately
HealthHub / Prototype interface

One day.
Two perspectives.

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

One personal dashboard in desktop and mobile layouts, using static demonstration values; the desktop layout is an authorial extension of the mobile cabinet.

Explore the scenario
Reading and action order

HealthHub

Prototype interface

  1. 1
    Mobile reading order: four health indicators
  2. 2
    Selected date and calendar context
  3. 3
    Medication and consultation cards
  4. 4
    Weekly activity for comparison

Adaptation through priority. The same blocks take different arrangements. Mobile prioritises the calendar while retaining the weekly perspective further down. The diagram describes the case logic. Working transitions are limited by the current prototype.

How the project
is presented.

The challenge, decisions and prototype are documented. The process history, contributors and intermediate versions still need supporting material.

My role

Visual identity and user interface design.

Already documented

One personal dashboard in desktop and mobile layouts, using static demonstration values; the desktop layout is an authorial extension of the mobile cabinet.

  1. 01

    Brief

    Scope documented

  2. 02

    Decisions

    Decisions and trade-offs documented

  3. 03

    Prototype

    Layouts available above

  4. 04

    Validation

    User testing remains a next step

What took shape.
Within the prototype.

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.

Health cards with units and trends
4

Artefact inventory

Responsive dashboard layouts
2

Artefact inventory

Event types: medication and consultations
2

Artefact inventory

The numbers describe the prototype’s scope. User impact has not been measured.

To add: baseline, test method, sample and results.

Boundaries of the result

Values are static, date selection does not update events, and navigation only changes active styling. The demo does not establish completed health actions. With no baseline or user testing, effects on understanding or daily habits remain unknown.

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