Salus: From a Feature-Stacked App to a Goal-Driven Nutrition Product

Redesigning the UX of a healthy meal subscription app and building its first design system from scratch

Salus Mobile Design System

Salus Mobile Design System

Salus Mobile Design System

Role Head of Product Design: UX strategy, UI design, design system
Product Salus, a healthy meal subscription app in Saudi Arabia (iOS & Android)
Scope End-to-end redesign across 12+ flows, a new design system, and a component library
Team 1 Product Manager, 2 mobile engineers, marketing & stakeholders
Timeline 2 Months

Salus had grown feature by feature: plans, a store, a wallet, referrals, and rewards. There was no shared design language holding it together. The app worked, but it felt like several apps stitched together. Every screen used yellow for something different, customers couldn’t see why one plan suited them over another, and people with expired subscriptions landed on dead ends.

I redesigned the experience around one idea: Salus shouldn’t be a menu you order from. It should be a partner that helps you reach a health goal. To make that consistent and buildable, I created the product’s first design system: foundations, components, product patterns, and accessibility rules.

“Built for daily progress, not daily friction.” This became the north star for the system and for the product.


1. The Starting Point: Auditing the Old Experience

Before I designed anything, I went through the live app screen by screen as a customer would: browsing, subscribing, managing a plan, and checking rewards. Then I logged every friction point.

The original Salus app

The original Salus app

The original Salus app

What I found

UX problems