Three screens from Ivím’s platform redesign, and the call behind each.

In-house at Ivím, 2026. Product design.

From July to September I designed about 25 screens for Ivím’s platform redesign. The journal, Purchases and Orders are live. Each turned on one decision.

Client work. Order numbers and product names in these screens are placeholders.

The story in four pictures

The journal on a phone, with a full day logged.

On desktop, from my prototype. The sleep card says the data is missing and never guesses why.

Purchases, memberships and orders in one list, from my prototype. Order numbers are placeholders.

Before, five boxes

After, the design that shipped (Figma)

The same details, in two regions instead of five boxes. Tap Shipping history to open it. The order number and product name are placeholders.

Problem

Unity is Ivím’s redesign of its whole product platform, made to feel more clinical and trustworthy.

The new glass look, which Ivím calls Liquid Glass, comes from that shift. I designed about 25 of its screens between July and September, while building the design system under them at the same time. That system is its own case study.

The journal, Purchases and Orders are live in the app, and each turned on one decision.

What I built

I designed screens across the platform, from the daily journal to purchases, orders, accounts, memberships, payment methods and programs.

Three of them get a closer look here.

The journal is where people log weight, steps, water and sleep. Steps and sleep can sync from Apple Health or Health Connect. I designed every state, from the first weigh-in to a sync that stops, and the desktop layout.

Purchases puts memberships and orders in one list, with shipment tracking and receipts. Orders shows one shipment, with when it arrives, where it is and what is in it.

The rest of what I designed for Unity, one line each.

Account details, where each field’s edit path depends on what it needs. Account navigation, where a chevron always means the screen pushes. Subscriptions and memberships, presented to product. Membership value, where access is the hero. Payment methods, rebuilt after the list screen turned out to have a Save button with nothing to save. Programs, where the treatment window starts on order. Billing history, moved to the foot of Orders with an 11-screen prototype. And No active orders, kept to the one page it needed.

The judgment moment

The journal can’t know why your steps are missing.

Apple doesn’t tell an app whether you turned off its access to Apple Health, so “you denied us” and “you walked zero steps” look the same. The empty state describes the absence and never guesses the reason, and offers Check in Settings or Log manually. Health Connect on Android does report it, so Android gets different copy.

On Purchases, I challenged the recommended status treatment and it didn’t hold up. It gave the one urgent state on the screen, a failed payment, the quietest treatment, one muted word. Checking the screen against product’s list also turned up 22 states the design didn’t cover, which I built out as a 25-frame stress test.

On Orders, a reviewer said “every piece of information is broken into its own box.” Shipment details went from five boxes to two regions, with all six tracking details kept. I built three directions to choose between in Figma, on the real background.

Proof

The journal, Purchases and Orders are live in the app.

Memberships are on the way, and their design will be updated before they ship.

Constraints

I designed each screen and made the calls; AI agents built most of the Figma frames from my specs.