Designing Holistic Ubiquitous Experiences
Christian Crumlish | UXI Live - June 17, 2013
I couldn’t help myself
• Designing Holistic Ubiquitous Experiences
• Christian Crumlish | UXI Live - June 17, 2013
but seriously, folks
First things first…
• Research first
• Understand customers first
• Design a holistic experience first
• Without regard to devices or endpoints
• Platform first, APIs first
and while I have you all here…
Mobile means ubiquitous
• It’s the user who’s mobile
• ―best screen available‖
• Mobile user journeys
• Product as service
• Holistic UX
Doing ―mobile‖ second at CloudOn…
• Tablet product came first
• Second device: a step back to holistic
• Assumptions vs. reality…
One info hierarchy – many screens
Some (painful) lessons learned
• Refactoring to a single codebase across device form
• App store hassles
―The install process is the worst on-boarding ever invented by
man‖ — Bill Scott
• Getting instrumentation right
• ―Going Mobile‖ – regularly walk around with the mobile
device, using phone connectivity, and try to GSD.
Holistic user experience
Holistic UX Layouts (via Luke W)
Map the ecosystem
• Product as service
• Device-agnostic experiences
• Concept modeling
• Extended user journeys
• Meet the user where they are
provide value before requiring commitment
Scenario sketching Customer runs CloudOn app and
connects to CloudOn via wifi.
Always work in parallel
Regardless of the ―main‖ task, always consider
Browser and native apps
Multiple operating system styles and conventions
Successive versions of OSes, devices, browsers
All form factors
…when designing your holistic UX
Landscape and portrait
Browser vs. client app
Browser vs. client app
When in Rome…
So when does Tablet First make sense?
Tablet first is our philosophy - and real
stats back it up. The issue is more people
still think laptop *only*.
— Paul McAleer, GoGo
… a strategy called “tablet first,” which assumes that
tablets are going to change how people work and will also
become the place where developers will create the most
innovative applications and websites.
―[Tablet-first design] brings into account things like swipe….
―Then if you start from there, then the mobile experience becomes a
relatively simple space-constrained version of the design, while the
desktop experience nicely generalizes this is what you do with the
mouse. But the devil’s in the details.‖
Sridhar Ramaswamy, Google SVP of ads and commerce
For devices that hit the market just three years ago, they're doing pretty well,
generating 8 percent of all Internet traffic. By Dara Kerr March 7, 2013 5:19 PM PST
The numbers are out -- people increasingly prefer to browse the Internet on
tablets rather than smartphones.
What type of experience?
• Focused, direct task?
Start with handheld
Get the basics right
Optimize the core experiences
• Creative, visually complex, spatially expansive task?
Start with tablet
(Especially for generative work, space matters)
Then expand the design ―down‖ (to mobile)
And ―up‖ to desklap
Tablet First benefits
• design ―from the middle out‖
• focus on a medium form factor
• support for portability
• think in terms of gestures
• address a mixed paradigm
– Prototype tablet experiences in the browser
– Tools like http://draggabilly.desandro.com/ can help with this
Director of Product
This is a longstanding venerable form factor, both portable and suitable for getting things done. This Roman-era tablet requires a stylus (pre-Steve Jobs).
For a visitor to Israel, getting through the passport line on arrival is a terrible first-time user experience. With 10 or more lines, one is nearly always in a slow one. A single snaking line looks worse but works much better. The Israelis in the audience don’t experience this and may not be aware of it. The lesson is to understand your users when their experiences are different from your own.
We thought people were *much* less likely to attempt editing and creation tasks on the tiny phone screen than they actually were.
Clockwise from top-leftwireframe with metadata area and activity streamTablet layoutPhone screens, one each for the activity stream and the metadataWeb browser layout (alpha)
DesignedAcross devicesAcross appsAcross online / offline divideAcross peopleExpressedPer device
LukeW offers many suggstions for how responsive designs might stack up in different layouts, all sharing the same information hierarchy.Investigate adaptive design for similarly responsiveness in client apps.
This is a CloudOn user on an airplane trying to reach our cloud services with iffy wifi.
Always consider portrait, landscape AND transitions between orientations
Browser experience gives greatest breadth(Note this is a preview of the browser alpha)
App experience can be more fine-tuned, closer to the device’s hardware capabilitiesLukeW calls this “reach” vs. “rich”I told him rich and reach are homophones in Hebrish
When developing for iOS and Android, how to balance the OS standards of each, while maintaining a unique style for your product?There’s no easy answer
the site has been rebuilt with a tablet-first approach, meaning that instead of starting with a PC and browser as our reference and then scaling that design down to mobile devices, our designers and engineers used mobile as a starting point and worked out from there
Kunesh: All of the web applications we built used responsive design [where the application reformats to the device being used], and most of them were built to target tablets first, then phones and laptops.
Battery Ventures has hired a new entrepreneur in residence – Charles Jolley, a former executive at Facebook and Apple – and has asked him to help the firm pursue a new investment strategy, VentureWire has learned.