The products we use are the result of countless compromises and tradeoffs before we even experience them. Every engineering specification, and every design decision, stems from discussions we’re not privy to about form, time, effort, budget, and so many other considerations.
Once a product is brought forth into the world, our individual experiences with it introduce context and variables that can stretch far beyond what its designers envisioned. How I use a product differs from how you use it, where you use it, when you use it.
I say this because last week, I wrote about the anti-experience of the Android operating system. My thesis was that Android is a loose collection of disparate experiences:
@devolute @RWD The right UX shouldn't be a game of Android Lotto.— Gregg Bernstein (@greggcorp) June 29, 2016
With all the thoughtful decisions that yielded the latest Android operating system, every phone carrier, manufacturer, and model adds a variable that yields vastly different outputs. Ethan Marcotte added the technical context I had neglected by linking to the slide deck in this tweet:
“If somebody tells you they tested their website on Android, laugh evilly and show them this slidedeck.”http://t.co/T14Upqoym5— Responsive Design (@RWD) July 14, 2014
TL;DR: the best possible version of Android is doomed to failure by an impossibility of contexts.
Ian Parr responded to my article:
@RWD @greggcorp I presume you’ve been told that you bought the wrong Android phone if you wanted the unified experience you talk about— devolute (@devolute) June 29, 2016
Similarly, Jiri Jerabek wrote:
@greggcorp Nexus is Google's 'North Star' for 3rd parties. I'm not sure whether what you described is a 'problem' for the majority of users.— Jiri Jerabek (@JiriJerabek) June 29, 2016
Both Ian and Jiri raise interesting points about the roles of North Stars and flagships, and where reasonable expectations give way to diminishing returns. A design North Star, as described by Facebook’s Julie Zhou, is an achievable, realistic, inspiring, and unifying vision. At its core, a North Star provides internal guidance to the team building a product.
Inversely, a flagship is the brand or service for which a company is most well known. The flagship is determined by audience size, sales figures, or popularity. It’s an outcome, not a goal. The Accord is Honda’s flagship automobile, just as the Air Jordan remains Nike’s flagship shoe and Windows arguably represents Microsoft.
With all eyes on a flagship, it’s incumbent on a company to reserve their latest innovations for these popular offerings. In Android’s case, we can see that updating their flagship Nexus phones has two potential goals:
- It signals that Google isn’t resting on its laurels
- It introduces a halo effect for the rest of the brand. That is, what’s seen in the Nexus is reflected to varying degrees in offerings from Samsung, HTC, Motorola, and on down the line.
And this illustrates the difficult position Android finds itself in, as their flagship Nexus phones are also positioned as partner-facing North Stars: beacons of achievable, realistic possibilities.
But possibilities yield to expectations. The expectation is that the innovations in the flagship will surface elsewhere, which for an Android purchaser is a risky proposition. What appears in the flagship, however tightly correlated to the North Star that brought it to life, has no guarantee of trickling down to mass production.