Portfolio · Product & UI/UX Design

Apprn — Product Design

Mobile app design and an AI-native design system for apprn — scoped as a design engagement, distinct from the venture build it now supports.

The scope

A design engagement inside a bigger bet.

apprn is one of our own ventures, and the venture log covers the thesis and the build end to end. This page is narrower: the product design and design-system engagement specifically — the mobile app interface, the two-role UX for owner and receptionist, and the component system underneath it — scoped and delivered the way a client engagement would be.

Framing it this way matters because the design work had to stand on its own: a future client buying only Creative Brand Build should be able to see exactly what that scope produces, without the venture-strategy narrative attached.

The brief

Two roles, one design system.

The interface had to serve an owner reviewing weekly numbers and a receptionist booking a chair between clients — different urgency, different literacy with software, same underlying data. The brief was one design system that could produce both without forking into two products.

The approach

Roles before screens.

01Role-based defaults, shared tokensOne component library, two default configurations — dense and data-forward for the owner, single-task and fast for the receptionist.
02Design in the build environmentScreens designed against real agent behaviour rather than static mocks, so the trust-building UI (propose → confirm) was tested early.
03System documented for handoverTokens and components shipped with documentation, so the product team could extend the interface without a design re-engagement.
Delivery

What the engagement produced.

01
UX research and role mapping
Owner and receptionist workflows mapped separately before any screen was drawn.
Weeks 1–2
02
Design system foundations
Tokens, type and component primitives built to serve both roles from one source.
Weeks 3–5
03
Mobile app interface
Booking, reminder and commission-dispute flows designed for both roles.
Weeks 6–9
04
Documentation and handover
Component library and usage guidelines delivered to the product team.
Week 10
Two-role component system
One design system producing an owner view and a receptionist view from shared tokens.
Booking and reminder flows
The interface for the agentic propose-and-confirm pattern.
Handover documentation
Component guidelines the product team extended without a re-engagement.

No — the venture log covers thesis, brand and build together. This page scopes just the design engagement, the way it would run for a client buying Creative Brand Build alone.

Yes. Product and UI/UX design plus an AI-native design system is exactly the Creative Brand Build engagement, run here on our own venture first.

Scoped to requirement

One judgement layer, not three vendors.

The value was never any single discipline. It is the seam.

Talk to the studio