Not long ago, a low-profile program called Android One looked like it could be just the one-two punch Android needed.

Android One, like lots of Google initiatives, has had a long and winding history with plenty of twists and turns. When Android One first came into the picture in 2014, it was described as an effort to "make high-quality smartphones accessible to as many people as possible." The focus was squarely on bringing affordable phones with exceptional experiences to emerging markets — places like Pakistan and India, where it could be "hard for people" to "get their hands on a high-quality smartphone," as Google put it at the time.

But that was just the start of Google's Android One ambitions. Three years later, in 2017, Google expanded the program with the launch of Android One phones in places like Japan, Taiwan, and eventually the United States. The company changed its description of the effort from that original small-scale focus to the much broader vision of a "collaboration between Google and [its] partners to deliver a software experience designed by Google," with a guarantee of reasonably timely ongoing operating system updates and an experience that'd be free from all the bloat and shenanigans baked into so many Android products.

Sound familiar? It should. It's basically the same concept we see with Google's own self-made Pixel phones, only scaled down a bit and with other manufacturers involved. Or, to zoom back even further into Android nerdland, it's incredibly similar to what we used to see with Google's Nexus phones many moons ago — where Google would bring in other phone-makers to handle the hardware but then maintain complete control over the software, support, and overall user experience itself. (In the Nexus scenario, of course, the phones were branded as Google devices. But that surface-level distinction aside, the situation is almost eerily comparable.)

https://www.computerworld.com/article/3613511/android-one.html