Next version of Android to be "previewed" at Google I/O tomorrow

Next version of Android to be
Sundar Pichai has confirmed that Google will show off the next version of Android at Google I/O tomorrow. The modus operandi for Google has been to announce and release a new major update to Android at the same time. On one hand, this is nice, because early adopters, Nexus users, and developers got the finished product without delay. But, it also came with issues, and it seems that Google wants to address those.

The number one issue was in that Android lived in a fuzzy area of "open source" where the code was open to all after the release, but not during development. We don't yet know if Google will be releasing the source code tomorrow or not, but it will be interesting to see. Android chief Sundar Pichai told Bloomberg Businessweek that he wants "the world to understand what we are doing sooner", and so Google will be showing off the next major Android update tomorrow, but Pichai didn't say anything about releasing the update to anyone. 

Aside from transparency and open source issues, it seems likely that there will at least be a beta release for developers, much like how Apple has been releasing iOS betas at WWDC well ahead of the full release in the fall. This should help Google mitigate issues that have plagued early adopters and Nexus users which had apps lose compatibility with newer versions of Android. And, it could help to minimize the long delay between the Nexus release and other major manufacturers pushing the update. It would certainly mean more manufacturers will be able to launch handsets for the holidays that run the newest Android version. 

We've seen various leaks that point to pretty big UI changes for Android on the way, and there have been rumors of an Android TV announcement, which would all be connected to the next version of Android.

FEATURED VIDEO

18 Comments

1. Derekjeter

Posts: 1456; Member since: Oct 27, 2011

If your a developer with Verizon how do you even get the new version of Android with out going through Verizon and adding all their bull spit bloatware? Just a question.

4. MichaelHeller

Posts: 2734; Member since: May 26, 2011

Not really sure how to avoid the bloat, only Motorola has done it recently. Carrier bloat is the last piece of the process. HTC detailed it all:http://www.phonearena.com/news/HTC-makes-an-infographic-to-detail-the-Android-update-process_id50719

9. jaytai0106

Posts: 1888; Member since: Mar 30, 2011

Unlock, root, flash, and no more bloatware. (Let's how I imagine it to be anyway XD)

14. Zylam

Posts: 1809; Member since: Oct 20, 2010

They wouldn't be a dev only on a Verizon phone, the base Android on Verizon phones is the same as any other Android Phone, a part from the crap big red add to them. They would probably have a normal Nexus device from the play store, maybe the phone and tablet and be testing their apps on that and release it for newer versions when they come out, doesn't really have anything to do with Verizon.

2. Chris_Bakke

Posts: 246; Member since: Jan 23, 2013

Further optimization is always welcome.

3. Vexify

Posts: 570; Member since: Jun 16, 2014

Im excited for this entire I/O :D

5. rob5150

Posts: 183; Member since: Oct 31, 2011

Just because Google is going to talk or show the new system doesn't mean they need to release it to the public.. Like the author made it sound. Open source software source code is made available when product of such open source software is released into the public

6. somad

Posts: 169; Member since: Apr 17, 2014

The new version of android must not go through Verizon or other carrier, it must go directly from Google to the android device. Google must do something about this, every time there is new version it takes months until we get it. Especially Verizon.

7. Lt.Green

Posts: 397; Member since: Mar 13, 2014

Yey! More fragmentation!...not.

8. jsze100

Posts: 3; Member since: Jun 13, 2014

Will probably be Android 5.0, new interface for better integration with their other products, and 64-bit support. Probably other enhancements and new features too.

11. juandante

Posts: 679; Member since: Apr 23, 2013

64 bit should already be possible (it is Linux). ™

12. tyger11

Posts: 286; Member since: Oct 29, 2012

Sort of Linux. The problem is Dalvik. Fortunately, Dalvik seems to be going bye-bye. This will help move Android to 64-bit, speed things up, and avoid irritating lawsuits by A Certain Company.

10. nasznjoka

Posts: 418; Member since: Oct 05, 2012

I don't expect much from this I/O event when android as long as android is concerned

13. Mark7

Posts: 21; Member since: Jun 10, 2014

does anyone knows how many licks does it take to get to the Tootsie Roll center of a Tootsie Pop

17. kdealltheway

Posts: 94; Member since: Oct 21, 2012

Around 800

15. Kenny_Strawn

Posts: 6; Member since: Oct 12, 2012

I can count at least three reasons why a beta release for developers (and a beta release of the source code) would be a good move by Google: * Developers: If the rumors about Google ditching Java entirely and requiring the use of Dart, HTML5, and/or JavaScript code to develop Android apps are any indication, this release could introduce some major API breakage ― heck, it would almost make it Android's iOS 7. So, releasing a beta version of Android should give registered Android developers ― that includes me ― ample time to get their apps ported and ready for the final release. * OEMs: Releasing beta versions of both the OS and source code (very likely) to limited audiences should give device manufacturers like Samsung, HTC, LG, Lenovorola (sorry, had to put that in there), and others ample time to port the latest version of Android to their devices ahead of the public release, oh, yeah, and also ample time to make sure their proprietary launchers/UIs also work on the new OS not after the public launch but before, these factors working together to ensure a far more rapid roll-out when the final release comes along. * Carriers: As we all know, more often than not, carriers end up also being developers at the same time. While, I agree, carrier-blocked updates can often occur for the outright dumbest of reasons (incompatible Windows-style carrier crapware apps ― come on), a beta release should definitely give carriers ample time to make sure compatibility situations like the above simply don't occur, and thus, further enhance the speediness of the rollout when the final version starts hitting devices. Bottom line: A beta means preparedness. Prepared carriers, prepared developers, and prepared manufacturers are obviously going to allow MUCH faster OS and app roll-outs than unprepared carriers, unprepared developers, and unprepared manufacturers the way they are right now. By making sure all the carriers, manufacturers, and OEMs are working together to roll the new OS out on a prompt basis by offering beta releases to prepare them, the result is ultimately a FAR faster rollout to users when the final release comes out than what we've seen in the past, and yeah, any fast rollout is indeed a good enough rollout to just about make me switch back to (any) Android device from iOS in December...

16. mistertimi

Posts: 77; Member since: May 28, 2014

Google ditching Java in favour of Dart?!? Hahah funny stuff.

18. emadshiny

Posts: 1144; Member since: Dec 05, 2012

Waiting to taste it on my Nexus5

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at https://www.parsintl.com/phonearena or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit https://www.parsintl.com/ for samples and additional information.