4 ms·
Let me offer a solution: It's time for Google to offer a Google+ Certification for Android. These certified devices would have two important characteristics: 1
by javajosh 14y ago
Let me offer a solution: It's time for Google to offer a Google+ Certification for Android. These certified devices would have two important characteristics:
1. They are guaranteed to run the latest version of Android for 5 years.
2. They are guaranteed to have a clean version of Android, without any carrier or device maker modifications.
No doubt the marketing people can come up with other things to add to the list, but that's the gist of it.
If such a certification existed, personally I would only shop among those options.
Such a certification would require that Google have some sort of compatibility criteria, and that their future development efforts run well within those criteria. So it constrains Google just as much as the OEMs. The certification should be cheap, but not free. And I picked the name for Sergey's buy-in.
The nice thing about this (voluntary) certification program is that OEMs don't have to participate. And in fact could have certified and uncertified devices. The program captures the essential qualities that made the iPhone successful, in my opinion. The App Store is a big part of their success, and developing for the iPhone is far more pleasant because of the stability of the platform.
EDIT: Okay, if it was 3 years I'd still be happy.
- timdorr 14y agoThis is great. The only thing I have a gripe with is: > They are guaranteed to run the latest version of Android for 5 years. 5 years is too long. The HTC Dream, the first Android phone, was released less than 4 years ago. It only has a 528Mhz processor and 192MB of RAM. I don't want to know what the ICS or JB experience would be on that device... Keep in mind the iPhone only turned 5 this year (the App Store turns 4 in a couple weeks). And the last version that supported it (with limited features) was released 3 years afterwards. I think 3 years is more reasonable. Most people are eligible for a discounted phone upgrade every 2 years. I think that would fit in for most folks.
- javajosh 14y agoYes, you're probably right. 3 years is more reasonable. For some reason I thought Apple was supporting 5 year-old devices, but they are not. And they are the ones setting the standard, here.
- spiralpolitik 14y ago2 years from the point that the phone model was last sold would be reasonable. Or to put it another way you should expect to receive software updates for the phone for the duration that you are still under contract.
- zanny 14y agoThe problem with this argument is that we don't have any more extreme strides in mobile performance in the next 5 years. We already have phones that can effectively run any intensity of "eye candy" with spiff - by the time such a policy came to market in 2 years, it would be 2014 - unless we have a revolution in tech that lets us crank up the ghz without dramatically increasing the voltage to match, any arm based device for Android will be able to run any degree of eye candy they can add in in the "short term". Back in 2008, we could easily see that the 500mhz single core ARM chip was going to be short lived. We had tremendous strides in performance available to us in just upping core clocks, and then we had the mobile multicore revolution. We are done with both the main vein and the secondary digs of the mobile CPU goldmine (in reference to Herb here) and we are already pretty deep into heterogeneous computing. Remote processing is next, when the telecom monopoly is torn down so we can get the data speeds we are actually capable of today without paying monopoly rates. The hardware WILL get significantly better between 2014 and 2019 - a 2019 smartphone will almost assuredly be as powerful as the 2014 consoles that will be coming out for gaming - but we can actually predict that. A 2014 console will have approximately a GCN 7850 graphics card and quad core 3.5 ghz cpu of some sort. So expect the mobile chip of 2019 to operate at ~4ghz with some number of cores and a lot of compute nodes approximately equivalent to modern mainstream desktop graphics at similar wattages to what we have now. If the version of Android in 2019 can't run on an Android device of 2014, then that isn't the hardware not keeping up with software - that is just terrible design. Just like how desktop hardware peaked in 2006, mobile hardware will peak soon as well, after which performance is "good enough" for average joe consumer, and the UX won't change. Another good example is how Google can keep pumping out new versions of Chrome without hesitation that the last version's user can run the new version. The browser is not getting exponentially more power or resource hungry, and in many ways they optimize its performance as much as they sacrifice it each release for better experience (of course things like webgl are pressuring browsers upwards with new usage in an environment without resource contraints) but the basic device, or in this case application, is not growing more and more computationally intensive by large jumps each release, or they would not be able to push out silent updates like they do. Same thing with Android. Once it plateaus, there is no excuse not to use the silent continuous always backwards compatble update model, because the device is now "good enough". Just like how a dual core 3ghz pc from 2005 with 4gb of ram is still good enough today for 95% of use cases.
- gardarh 14y agoI sincerely agree. However 5 years is a long time, perhaps 3 is more appropriate. Keep in mind that the first iPhone was introduced 5 and a half years ago.
- AndrewDucker 14y agoFive years is ridiculous. The phones three years ago are vastly less powerful than the ones now - building Android so that it definitely fitted onto them would be nigh impossible.
- glogla 14y agoFive years is a really long time in the mobile industry, and will be for the coming decade, even if the crazy tempo is slowing somewhat. According to wikipedia [1] typical high-end 2009 phone (which is just three years) had 256 MB RAM and 600 mhz ARMv6 processor. I think two or three years would be enough, with todays rate of improvement. Other than that, it's a great idea. [1] https://en.wikipedia.org/wiki/Comparison_of_Android_devices https://en.wikipedia.org/wiki/Comparison_of_Android_devices
- WrkInProgress 14y agoAren't you essentially describing the Nexus line of devices, minus the the tad unrealistic 5 years of software updates ?
- javajosh 14y agoActually, no. My Nexus One was less than two years old when Google announced that it would not receive an ICS (Android 3) update.
- johsoe 14y agoThat wasn't really a political decision, but a design error. The internal storage is way too small on the Nexus One. The same reason HTC Desire barely could get gingerbread.
- natrius 14y agoGoogle announced their solution to this problem at the last Google I/O: the Android Update Alliance. It was basically a commitment by manufacturers to update phones for 18 months following their release. This is how it has panned out so far: http://www.pcmag.com/article2/0,2817,2397729,00.asp http://www.pcmag.com/article2/0,2817,2397729,00.asp tl;dr: As of December 2011, only Sony had lived up to its pledge. HTC came close.
- javajosh 14y agoThank you natrius for that link. I'd never heard of the Android Update Alliance before. It is indeed very similar to what I'm proposing, and it's sad to see that it didn't take the first time around. I think it's worth trying again, perhaps under a new moniker, and with some changes. One big change is option #2 - no device or carrier modifications. That means that the onus really isn't on the manufacturer to support an upgrade, other than getting the initial certification. After that step is taken, they have Google's assurance that future updates will run on the device. Another potential change would be for Google to spend some marketing dollars on the initiative. Finally, Google could make certification a required part of the Android licensing process. It becomes a non-voluntary program. The drawback to this, of course, is that it raises the bar on all Android phones, probably reducing the cheapest options to close to zero. (Although, who knows? I'm not a marketer or analyzer of markets. I truly have no idea what this change would do to the Android landscape, and I'm sure there are people with comfy 6-figure salaries at Google and the OEMs that can answer this question with more confidence, if not more certainty.)