← Back to work

Wearable tech · Identity access · ZCloud ecosystem

IDZ

Designing a stylish wearable that gave people secure access to personal information when it mattered most.

IDZ explored a more focused kind of wearable experience — not a smartwatch overloaded with features, but a stylish object with a clear role. The product combined a wearable identity-access experience with ZCloud, a secure ecosystem for storing, organising and accessing personal information when needed.

Product area
Wearable identity access / secure personal information
Focus
Physical-digital UX, onboarding, trust, security and companion-system design
Role
UX/UI design, concept exploration, interaction design, product-system thinking and prototype testing
Scope
Wearable flows, onboarding, lock interaction, product configuration, ZCloud document management
Status
Concept developed with real working prototypes used for exploration and testing
Hero
The moment IDZ is really about — a stylish object, held in the hand, quietly asking for a secure interaction before it opens up.

01 / Context

A wearable that did less — but mattered more

IDZ explored a different kind of wearable value, focused on one clear promise rather than a long list of features.

Instead of chasing an everything-device, the product focused on a smaller, more practical promise: giving people secure access to the personal information they actually needed in real situations.

That meant designing beyond the object on the wrist. The experience also had to include trust, onboarding, a clear interaction model, and a secure ecosystem for storing the information behind it.

03 / Teaching the interaction

Designing for an unfamiliar physical interaction

The experience depended on the physical watch itself. The interface had to teach people how to use the product, not only what it did.

Onboarding
Onboarding treated the physical act — putting the watch on — as part of the flow, not an assumption.
01
02
03
04

A four-step bezel-based lock flow — teaching people how to rotate, understand progress, confirm digits and complete setup with confidence.

Instead of relying on a standard touchscreen pattern, the interaction needed to teach a new gesture clearly, reduce uncertainty during secure setup, and keep the experience calm and elegant throughout.

04 / Designing trust and security

Security had to feel understandable, not intimidating

Because the product centred on personal information, trust was part of the experience from the beginning.

The lock flow was not only a security step — it was also a UX problem about reassurance, clarity and control. The interaction needed to make security feel embedded and intentional rather than hidden or overly technical.

The best secure interactions often feel simple only because the explanation behind them was designed well.

05 / Ownership and setup

Ownership started before the watch was even on the wrist

The experience extended into configuration and ownership too — framing IDZ as a product system rather than an isolated interaction.

Configure
Choosing a variation, understanding the product and moving into a purchase flow — brand, product and ownership joined into one journey.

06 / ZCloud ecosystem

The secure system behind the watch

ZCloud was the practical ecosystem that made IDZ useful beyond the wrist — a secure space for personal information and document access.

File details
A single, focused file view — metadata, actions and sync control kept calm and legible.
Folders
The folder view — the entry point to secure documents the wearable could reference.
Upload
Filter & sort
Add

Supporting states — upload, sort and add — kept as small utility moments rather than a gallery, so the ecosystem read as one calm product surface.

Secure document access

Personal information stored intentionally, retrievable when needed.

Clear file mechanics

Folders, favourites and sync states designed to be scannable.

Practical over novelty

Utility that supported the wearable's promise, not an app for its own sake.

Product continuity

The watch and companion system read as one connected experience.

07 / Concept exploration

Exploring the shape of the experience

Early concept work explored how the interaction language might behave across the watch and surrounding product system.

Process artefact
Sketch-stage thinking about movement, icons, transitions and how the product might communicate value beyond a conventional app pattern.

Kept intentionally rough — a reminder that the interaction language for a new kind of product deserves exploration before it deserves polish.

08 / Real prototype testing

Designing with the real watch in hand

One of the most exciting parts of the project was that the work did not stay purely theoretical.

Prototype
Pairing tested against a real device — the IDZ watch and companion app together, not simulated on-screen.

Real prototypes existed, which meant ideas could be explored and tested against an actual physical object rather than only simulated on-screen.

That changed the quality of the design thinking. Pairing, physical scale, crown interaction and the relationship between the watch and phone could be tested against an actual device.

This is the kind of project that reminded me how exciting wearable design can be.

09 / Outcome

What this project sharpened

IDZ strengthened several parts of my design thinking at once.

Beyond flat screens

Designing for a physical device changed how I thought about interface constraints.

Teaching new gestures

Making an unfamiliar interaction feel obvious through clear onboarding.

Physical + digital UX

Treating the watch, phone and companion system as one experience.

Designing for trust

Making security feel embedded and calm rather than technical or hidden.

Ecosystem thinking

Designing the system around a user need, not just an isolated interface.

Style with utility

Holding elegance and practicality in the same product without compromise.

10 / Reflection

Why this project still stands out to me

IDZ sat at the intersection of product design, wearable interaction and ecosystem thinking.

It asked a different question from many digital products: not how to add more features, but how to make one focused promise feel elegant, useful and trustworthy.

It also reinforced something I still care deeply about: great product experiences often come from designing the entire system around a user need — not just the screen they happen to touch first.