One app, many policies.
An app for employees whose company relocates them abroad. No two employees get the same package, so one fixed interface could not fit them all. I designed it so the rules decide what each person sees.
- Role
- Lead Designer
- Timeline
- 2024–2025
- Platforms
- iOS + Android
- Team
- Solo Designer, Global Product Manager
Four problems, solved
Problem 01
Halfway through a move abroad, people want to know what happens next, not where their paperwork is.
Solved
The first screen is the move itself: where things stand and what comes next.
Problem 02
One app has to serve people whose packages have little in common.
Solved
The rules decide the view: each person sees only what applies to them.
Problem 03
Limits that show up only after a request cost time and trust.
Solved
Limits show before the action, and every no comes with a reason.
Problem 04
Access that grows one exception at a time is hard to trust and to check.
Solved
Roles decide who can approve, and every exception shows who made it and when.
From rules to screens
Rules first, screens second.
When every customer buys something different, I do not design one screen per customer. I map the rules, turn them into modules, and design every state a person can land in.
Step 01
Map the rules
Who decides what, and where it varies from one customer or person to the next.
Step 02
Turn rules into modules
Each part of the product can be on, off or limited, with no special screen for anyone.
Step 03
Design every state
Full, partial, empty and refused. Each one tells the person what happens next.
About this case study
This is client work under NDA. Some screens are shown with the client’s permission; the numbers stay with the client.

