Your product probably lives on a phone, a watch and a screen you don’t control. Multi-device ux design works when behaviour, wording and timing stay consistent while each device’s look adapts.
This page sits within the broader topic of iot user experience design, and it focuses on keeping one product coherent across many screens.
| Item | Value |
|---|---|
| iPhone share of the US market | 65% |
| Android share of the global market | 71.35% |
| Android users worldwide | 2 billion |
| Year interusability was coined (Denis and Karsenty) | 2003 |
| Components of interusability | Three: continuity, composition, appropriate consistency |
| Cs in the Adobe XD interview framework | 4 Cs |
The figures come from UXPin’s cross-platform guide and Adobe XD’s multi-device strategy interviews. Market figures can change, so check the source before you rely on them.
What multi-device ux design covers
A cross-platform experience means one product serves people on web, mobile, tablet and wearables, across operating systems such as iOS, Android, Windows and Mac. The aim is that users can reach the same features and finish the same tasks whichever device they pick, as UXPin explains.
Responsive design is narrower: it covers how a web interface looks across desktop, tablet and mobile viewports. Cross-platform work also spans native apps and operating-system conventions. Even a simple alert component looks completely different across iOS, Android, Windows, macOS, Safari, Chrome and Edge, per the same UXPin guide.
The real test is handoff. You can start an email in the Gmail mobile app, save it to drafts and finish it later on a desktop computer. That kind of continuity is what users notice when it goes missing.
Why one device is never enough
In the United States, iPhone holds a 65% market share, yet UXPin counts 2 billion Android users worldwide, a 71.35% share. In some countries Android makes up more than 90% of the market because iPhones are unaffordable, according to the guide. Treat these as a snapshot, not a forecast.
Serving only one platform also has an inclusion cost. The guide argues that a product that only works well on Apple devices excludes a large part of the global population, including communities who can’t afford those products.
Netflix is the guide’s example of scale: viewers can watch on mobile phones, tablets, laptops and smart TVs. Each category contains many devices, operating systems and screen sizes. In an IoT setting the same problem spreads across sensors, hubs, wearables and apps.
What to keep consistent and what to let vary
UXPin is blunt that pixel-perfect sameness is out of reach across platforms. What designers can control, and should keep consistent, is the list below.
- Messaging: the words and labels people read.
- Interactions: what an action does, wherever it is triggered.
- Performance: how quickly each device responds.
- Timing: when prompts, confirmations and updates arrive.
The rest can follow the device. Interusability calls this appropriate consistency: balance UI consistency with native layouts and patterns. Patrick Haney, quoted by Adobe XD, advises that when in doubt you follow the expected design patterns for a device instead of breaking people’s learned behaviours; see the Adobe XD interviews.

Frameworks you can borrow
Interusability
Charles Denis and Laurent Karsenty coined interusability in a 2003 publication, “Inter-Usability of Multi-Device Systems – A Conceptual Framework”, per UXPin. It names three components for coherent cross-platform experiences:
- Continuity: a seamless flow of content and interactions across products, tools and devices.
- Composition: organising functionality across products and devices.
- Appropriate consistency: weighing UI consistency against native layouts and patterns.
The 4 Cs
Adobe XD’s interviews describe a framework of the 4 Cs. Patrick Haney builds on Michal Levin’s framework from the book “Designing Multi-Device Experiences” and adds an extra C; the details are in the interviews.
- Consistency: follow expected patterns, for brand recognition and for usability.
- Continuity: plan and design the entire customer journey.
- Complementary: devices must work with other devices to get things done.
- Contextual: deliver the right thing at the right time, to the best available device.
Object maps and “devices as portals”
Sophia Prater argues that your websites, apps and Alexa skills are not products but portals to your content. She starts by modelling the objects in the environment, using Delta Air Lines as an example: flights, trips, airports, gates and seats. An object map answers what the objects are, what their structure is and how they relate, as Adobe XD reports.
Pairing an object map with iot personas shows which people reach which objects, and on which device.
Design systems, context and performance
Sarah Federman of Adobe says a design system breaks the UI into reusable parts and creates interactions users recognise across devices. A share flow, she says, should feel cohesive across devices and across the applications in an ecosystem, as Adobe XD notes.
Chris Risdon suggests drawing an empathy map for a user on one device, then lining up maps for different devices and moments. Patterns that emerge help you unify the experience, while differences show where to tailor it. His rule of thumb is to meet users where they’re at.
Performance belongs in this picture too. Federman warns that rich imagery that costs $3 to download in a developing country, or 10 minutes on hotel Wi-Fi, doesn’t actually help anyone; the quote is in the Adobe XD piece.
Permissions and data choices also have to read the same way on every screen, and the notes on iot privacy ux look at that side of the problem.
A practical checklist
Use these steps as a working order for a new or existing product:
- List the objects your product is made of, and how they relate.
- Rank what users want to do with each object.
- Note how well they can do it today on each device.
- Fix the things that must never vary: messaging, interactions, performance and timing.
- Move reusable parts into a shared design system.
- Test a handoff by starting a task on one device and finishing it on another.
Frequently asked questions
How is cross-platform design different from responsive design?
Show answer
Responsive design is about how a web page resizes to fit a screen. Cross-platform design goes further and includes native apps plus the conventions of each operating system.
Should every device show the same interface?
Show answer
No. Aim for familiar behaviour rather than matching pixels. Keep wording, actions and speed predictable, and let layouts follow what each device’s users already expect.
What does interusability mean?
Show answer
It is a term for how coherent a product feels as people move between devices in a connected ecosystem. Continuity, composition and appropriate consistency are its building blocks.
Where should a small team start?
Show answer
Begin with an object map and a ranked list of user goals, then check each goal on each device. Gaps in that grid show you where to spend design time first.
