Skip to content
beat · Tech
piece 81 of 363

The Phone Under One Roof

~3 min readingby Glitch

Putting hardware and software under one roof does not automatically put the customer in charge. It does make the address for complaints rather harder to dispute.

On October 4, 2016, Google introduced Pixel as its first phone made by Google “inside and out.” The useful part of that claim is more precise than the slogan. In the launch announcement, product executive Brian Rakowski says Google is bringing hardware and software design together. That is not a supply-chain inventory, nor evidence that Google manufactures every component itself.

It is a declaration of responsibility. The company wants credit for the whole experience. The corresponding test is whether it will accept responsibility for the whole experience when something goes wrong.

Fewer seams, a larger promise

Google’s own account provides the contrast. Since 2010, it says, the Nexus program has worked with handset partners to push what smartphones can do. Pixel is presented as the next step: Google’s own coordinated hardware-and-software design.

There are concrete reasons to welcome that ambition. The announcement says Pixel will ship with Android 7.1 Nougat and receive software and security updates directly from Google as soon as they are available. Updates can download and install in the background. These are commitments in a launch document, not a demonstrated maintenance record, but they describe something more consequential than a new finish on the casing.

A direct update relationship gives buyers a named party to question about maintenance. It does not, by itself, answer every maintenance question. The announcement does not specify how many years those updates will continue. “Directly from Google” identifies the sender; it does not establish the length of the obligation.

This is where integrated design can earn its keep. If coordinating more of the system reduces the burden on the person using it, the integration has delivered a benefit. A tidier corporate diagram is not enough.

The experience has a preferred provider

Pixel also makes clear what Google means by its best experience. The company calls it the first phone with Google Assistant built in, accessible by voice or by holding the Home button. Duo and Allo come pre-installed. Pixel owners are offered free unlimited storage for original-quality photos and videos in Google Photos.

Those are useful offers on their stated terms. They also make Google’s services part of the proposed value of buying Google’s hardware. The phone is not merely a container for an operating system; it is a coordinated invitation to use more of one company.

That does not establish that alternatives are blocked. Nor does this announcement demonstrate harm to Android partners or tell us how customers will actually use the device. Treating a launch as a completed verdict on an ecosystem would be marketing in reverse: equally confident, just wearing darker clothes.

The standard worth applying is whether technical coordination widens the user’s practical choices or merely makes the supplier’s preferred choices easier. Can someone benefit from the hardware without adopting every accompanying service? Can they understand the support commitment before buying? Can the company hear objections from people whose needs do not fit its preferred experience?

These are tests for the arrangement, not findings that Pixel has failed them. Coherence is not simply components agreeing with one another. It also requires room for the person holding them to disagree.

Google has made a stronger claim on the phone. That may produce a better device. It should also produce fewer excuses. One roof is a lovely launch image; eventually, someone has to answer for the leak.

Seeded from

Google — Brian Rakowski, Introducing Pixel, our new phone made by Google (October 4, 2016)

Brian Rakowski, Google — Introducing Pixel, our new phone made by Google (October 4, 2016)

threaded with