HELIOS NYX CORE CANARY Legacy archive ↗

Direction generated · Core acceptance pending

03 VP2 design
+ approval.

Three representative families established the new native language. Every other contracted surface was mapped before production, and the actual build is now available in Tab 04.

Open the new Helios mobile mockups ↓
8versioned artifacts
984validation cells mapped
10references traced
Liosupporting character

03.1 / Outside research

Real inputs.
Deliberate borrowing.

VP2 received the actual retained images from Helios, Linear, Calm, Airbnb, and Duolingo. It extracted hierarchy, pacing, interaction, and emotional guidance while explicitly rejecting their brand identities and protected assets.
OLD HELIOS · INPUT ONLY Legacy Helios care list with stacked rounded cards
Rounded avatar cards, no persistent application shell, and weak operational state hierarchy.
NEW HELIOS · VP2 OUTPUT New Helios care list with edge-to-edge operational rows and bottom navigation
Edge-to-edge hierarchy, explicit sync and review states, shared navigation, and the recognizable palette used in a new system.

03.2 / New mobile mockups

The new Helios.
iOS + Android.

Care List establishes the primary shell, Daily Check-In proves a complex input workflow, and Alert Review Queue proves state-heavy operational hierarchy.

03.3 / Supporting character

Meet Lio.
Warmth with boundaries.

Lio guides patient-facing progress and recovery moments. Clinical alerts, PHI-heavy screens, security, consent, and destructive actions remain character-free.

Placement rules

    03.4 / Visual system

    Old colors.
    An entirely new feel.

    The recognizable base palette remains visible, while accessible action/text variants fix contrast. Typography, spacing, radius, elevation, and motion are explicit—not guessed by feature workers.

    Inter / title

    Care that feels clear.

    Inter / interface

    One restrained native family for titles, operational status, forms, and persistent state.

    03.5 / Global shell

    Shared chrome
    before screens.

    The operating system owns its bars. Nyx owns safe-area consumption, four-destination navigation, headers, containers, overlays, feedback, keyboard behavior, and global states.
    System safe area
    ContextAction
    Operational summary Edge-to-edge list Persistent state
    CareCheck-InMessagesSettings

    03.6 / Component + interaction contracts

    Every state
    has behavior.

    Controls cover loading, disabled, focus, validation, offline, duplicate submit, reduced motion, destructive confirmation, and platform-native behavior.

    Components

    Interaction rules

    Asset direction

    03.7 / Every remaining concept

    Thirteen screens.
    Nothing invented later.

    These are deliberately low-fidelity. The complete polished screenshot matrix is generated only after implementation, during validation.

    VP2 packet validation

    Loading validation…

    Download the complete sanitized VP2 packet

    Eight manifests, validation report, twelve renders, thirteen wireframes, Lio artwork, and SVG sources.