Work 01

SkinPair

A skincare routine builder that starts with the product you already love.

Type Concept project
Scope Strategy, UX Design, Visual Design
Year 2026
Status In development
The problem

The skincare industry is worth billions, yet most people have no idea whether their routine is actually working. They buy products that conflict. They follow advice written for someone else’s skin. They layer things in the wrong order. They waste money on routines that don’t work.

The problem isn’t lack of products. It’s lack of the right framework to make sense of them.

Existing apps approach this from the wrong direction — they start with ingredients, databases and clinical data. That’s not how people relate to their skin. People start with what they already have. What they already trust. What they already love.

The insight

Nobody starts from zero. Everyone already has at least one product they trust — a moisturiser that finally works, a serum a friend recommended, a cleanser they’ve used for years. That product is the anchor.

SkinPair flips the model. Instead of asking someone to build a routine from scratch against a database of ingredients, SkinPair starts with the product they already love and builds a compatible, complete routine around it. Or, for someone starting fresh, it builds one from their skin profile alone.

Start with what you love. Build from there.

SkinPair concept overview
Onboarding

Before someone builds a routine, they need to understand why they need one. The onboarding sequence acknowledges the frustration, validates it without shame, then reframes what’s possible.

Onboarding screen 1

01 — Acknowledge

“You’ve spent time, money and trust on your skin. Not all of it paid off.”

Onboarding screen 2

02 — Validate

“Conflicting ingredients. Mismatched products. Routines borrowed from strangers. It’s not your fault.”

Onboarding screen 3

03 — Reframe

“Good skin isn’t luck. It’s knowing what works, for you, specifically.”

Onboarding screen 4

04 — Introduce

“Start with a product you already love, or start from scratch. Either way, SkinPair makes sure everything belongs there.”

Onboarding screen 5

05 — Invite

“Ready to meet your skin properly?”

Click any screen to view full size

Key decisions

Routine role over match percentage

Most competitor apps show a percentage match. “82% compatible.” But a number doesn’t tell you anything useful. SkinPair instead shows every product’s role in a routine — cleanser, treatment, moisturiser, SPF. It shows what you have, what’s missing, and what fits. The frame shifts from clinical to intuitive.

People-first entry point

The user answers questions about their skin first, then inputs their favourite product. SkinPair can then immediately show how that product serves their specific skin profile — making the first moment of value feel personal rather than generic.

Tone as differentiator

The category is clinical. Ingredients lists, pH levels, percentages. SkinPair positions itself as the knowledgeable friend — someone who knows the science but talks like a human. The tone is honest, warm and non-judgmental throughout.

The interface

Premium emotional design as the primary differentiator. The category feels clinical. SkinPair should feel like the knowledgeable friend who actually cares about your skin.

Competitive landscape
SkinSort Strong conflict detection and community layer. Clinical design feel. Uses blunt match percentages.
OnSkin 100% unbiased, no brand partnerships. Scientific rating system. Trust is the core USP.
Skin Bliss AI face and shelf scan. Moving fast with AI integration. Technically impressive.
SkinPair edge Design quality and emotional positioning. Premium, warm, human. The knowledgeable friend the category is missing.
Reflection

SkinPair is a concept project — but the thinking behind it is real. The problem is real. The competitive gap is real. The design decisions documented here were made with the same rigour I bring to every brief, paid or not.

This project exists because the best creative decisions happen before anyone opens a file. The question “why does this experience feel wrong” came first. The design followed.

Have a problem worth solving? Let’s talk.