Martina M. FunakiMartina M. Funaki
UX/UI, component systems & handoff

Designing modular profile screens for 8 account types

Nester had eight kinds of account. Mapping which features each one truly needed collapsed them into four screens built from three reusable cards — with every field editable in place.

{{ m.label }}
{{ m.value }}

In action

Clicking a field activates only its own card: Cancel appears and Save turns on once something changes, while the other cards stay read-only. After saving, the card returns to its inactive state with the new values in place.

Groups 3, 7 Personal and professional details Last name changed to Smith and saved, then the company name changed to Sunrise Realty and saved.
Groups 2, 4 Professional access Mary Amstrong’s buyer access moved to View Only and seller access to No Access. Cancel and Save appear with the first change.

8 account types, 8 screens requested

Nester had 8 kinds of account: buyers, sellers, owners, professionals and their combinations. The client wanted as few screens as possible to save on design and development time. A separate profile screen for each account type would have meant 8 screens to build, test and keep in sync.

So before drawing anything I mapped which features each account type actually needs, and looked for the overlaps.

Features matrix per user type
{{ c.label }}
{{ r.feature }} {{ cell.mark }}
* if user has different properties that are connected to different professionals
** inform the professional that this will not affect their branding
The overlap

Matching user groups with identical feature sets told me how many versions of the profile screen actually had to exist.

{{ g.ids }} {{ g.who }}
8 → 4
screens to design
and build
The four screens those groups needed
Group 1, 5, 6 {{ gCap0 }}
Group 2, 4 {{ gCap1 }}
Group 3, 7 {{ gCap2 }}
Group 8 {{ gCap3 }}

Interaction decisions

{{ d.kind }}

{{ d.title }}

{{ d.body }}

{{ d.why }}

Iterations

The client asked for fewer steps and fewer pop-ups. I compared what the site already did against every version I drew, on those two terms.

{{ c.label }}
{{ v.name }} {{ v.editing }} {{ v.steps }} {{ v.popups }} {{ v.verdict }}

Reusable cards

Those four groups became three reusable cards. Each card owns one set of data, appears only for the groups that need it, and is built once — so the client paid for three components instead of eight screens. Editing happens inside the card that owns the data; the only modal left is the one confirming a professional change.

Alternative considered
Edit in pop-up modals
Why I proposed it

The rest of Nester already edited in modals, so it matched what users knew.

Why we didn’t

The PM wanted fewer screens to build and more reusable parts. Inline cards won; I kept one modal for the irreversible professional change.

Card {{ c.n }}

{{ c.title }}

{{ c.holds }}

{{ c.shownTo }}

Reflection

{{ r.label }}
{{ r.body }}
← Personalising a business profile Service design in SMB →