zlacker

>>skille+(OP)
This is a really great step in the right direction, especially with the updates and repairability offered by iFixit with Google partnership. The only fear I have is what if Google shuts down the Pixel line or whatever because they are not doing well a couple of years down the line? Traditionally, they have not been great at keeping their promises. Hopefully Samsung follows the lead set by Google.

>>nblgbg+Ul
They're on year 8 of Pixel (and 13 years of selling phones directly) and year 15 of Android. These aren't exactly likely candidates for killedbygoogle.com anymore

>>kllrno+fq
I guess only time will tell. Google also had Nexus from 2010 to 2016. Who’s to say the Pixel line won’t see a similar demise (and as a tangential point, probably an abandonment of support) in the next few years?

With the Chromebook obsolescence fallout and the decision to extend software and security support for those recently, one would assume that the Pixel may be subject to similar thinking within Google. But the sales volumes of Pixel phones are a lot lower than Chromebooks. Google doesn’t seem to generally handle hardware quite well.

>>AnonC+DA
Nexus was just re-branded to Pixel, they didn't abandon Nexus at all during that branding change.

You can see the full OTA history for every device going all the way back to the Nexus S:

https://developers.google.com/android/images

Note that there's no weird gap around the transition from Nexus to Pixel, both were supported concurrently during the overlap.

>>kllrno+hH
I think it was more of a rebranding, at least from Pixel 2 and onward. Nexus devices were often primarily designed by another manufacturer with Google oversight.