Skip to content
Apeiriion.

Case study · 2025

Healthcare & Wearables

Wearable health OS for watchOS and Wear OS

watchOSWear OSFlutterBLEUI/UX
VitaBand Health OS

Client

Digital health clinic network

Engagement

Wearable OS · watchOS & Wear OS

Duration

9 months

Year

2025

Overview

What we set out to solve

VitaBand unified vitals collection across Apple Watch and Wear OS with a Flutter companion. Product and interaction design lived in Figma first — complications, companion screens, and a shared token library — before native and Flutter implementation. BLE sync and consent-aware export give clinicians continuous signals while patients keep transparent controls over what leaves the device.

A dual-platform wearable suite syncing vitals to Flutter companions with privacy-first data handling.

Narrative

How the engagement moved from constraints to a shippable system.

01

Challenge

Clinicians wanted continuous wearable signals, but patients used mixed Apple and Wear OS devices with inconsistent apps.

02

Approach

We built native watch experiences plus a Flutter companion, with BLE sync and consent-aware data export.

03

Solution

VitaBand unifies vitals collection across platforms while keeping patient controls transparent.

Scope

What we delivered

Figma design system for watch + companion surfaces

watchOS and Wear OS native experiences

Flutter companion app

BLE sync and background collection strategies

Consent and privacy export flows

Clinician dashboard feed integration

Privacy counsel review package

Highlights

What stood out

Daily active wear adherence +31%

Unified clinician dashboard feed

Consent flows reviewed with privacy counsel

Figma tokens kept watch and phone UX in sync

Engagement flow

A repeatable rhythm from discovery through hardening — tuned to this product’s constraints.

01

Clinical & patient needs

Aligned vitals priorities, consent expectations, and mixed-device reality — then mapped flows in Figma.

02

Design system & prototypes

Built Figma libraries for complications, companion screens, and motion specs before engineering scaled.

03

Native watch builds

Shipped watchOS and Wear OS collection experiences against the design system.

04

Companion, sync & clinic pilot

Built Flutter companion with BLE sync, then piloted with clinics and iterated on battery and UX.

Technology stack

The delivery stack behind this engagement — client surfaces paired with services, data, and infrastructure.

Wearables

watchOSWear OSSwiftKotlin

Companion App

FlutterBLE SyncUI/UXFigmaDesign Systems

Backend

Node.jsREST APIsConsent-aware ExportSecure Storage

Outcomes

01

Daily active wear adherence +31%

02

Unified clinician dashboard feed

03

Consent flows reviewed with privacy counsel

Looking ahead

Add on-device anomaly hints and tighter EHR write-back paths.

Onboard the Apeiriion express

Tell us about your product, platform, or modernization goal — we'll assemble a senior squad and a clear delivery plan.