Google Delivers Android O Developer Preview 3

Posted on June 8, 2017 by Paul Thurrott in Android with 9 Comments

Google Delivers Android O Developer Preview 3

Google announced today that it has finalized Android “O” Developer Preview 3, offering developers their first peek at the final APIs for this release.

The firm says it now expects to deliver a 4th Developer Preview in July, alongside near-final system images for supported devices. And then it will release Android 0 to consumers “later this summer.”

But let’s stick with Developer Preview 3 for now.

As with previous releases, Android O Developer Preview 3 is designed to help developers update their apps for the new OS version. But this one is particularly important because it features the final (level 26) APIs for Android O, meaning that things won’t change for developers between now and the consumer release of the OS. (They did change between the previous two developer preview releases.)

And while there are no new features, Google is reminding developers about some of the new Android O features they should consider supporting.

“Notification channels and dots give you more ways to surface new content to users and bring them back into your app,” the firm notes. “Picture-in-picture keeps your app onscreen while users are multitasking, and autofill makes it simple for them to enter forms data and helps keep their data secure. Also check out adaptive icons, XML font resources, downloadable fonts and emoji, autosizing TextView, AAudio API, and many others. You’ll also want plan your support for background execution limits and other important changes in vital system behavior for O apps.”

Developers who are interested in supporting new Android O features should of course visit the Android O Developer Preview website.

And if you’re interested in testing this release, as I am, you will need a compatible device, as always. These include the Pixel, Pixel XL, Pixel C, Nexus 5X, Nexus 6P, and Nexus Player.


Tagged with

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (9)

9 responses to “Google Delivers Android O Developer Preview 3”

  1. Nicholas Kathrein

    If your not a dev your better off waiting. Using betas usually give your random studders and freezes and jank and you really only have to wait 3 to 4 months for the final software.

    • SvenJ

      In reply to Nicholas Kathrein: That's typically my advice too. Since my Pixel isn't my primary device, though, I went ahead and entered the beta as soon as it was available. I've really had no issues. Not sure it isn't more stable than my release OS Lumia 950XL.

  2. skane2600

    With Android Nougat at less than 10% market share, it doesn't seem like developers have to rush out and prepare for "O".

  3. rameshthanikodi

    A nice new feature in this build - music notifications are now tinted with colors that match album cover art

  4. Jorge Garcia

    Ok, say, I have a nice tablet that runs Android "O", is it too much to ask that when I attach a keyboard to this tablet, that the interface automatically recognizes and switches (or better yet, "asks" me whether to switch) to a trackpad-friendly, right-click-able, windowed interface with drag and drop? Come on, Google, it can't be THAT hard to do if Samsung just did it as a "side-gimmick" simply to add one more special feature to their flagship S8 phone. Further, Sentio, Remix, and Phoenix, all start-ups, have been able to muddle through this software problem as well. Apple's own iOS approach, which, to me, is headed in the right direction, is still all wrong in its execution. They are just mashing and layering productivity features into/onto iOS to the point where the interface will do neither the mobile experience well nor the desktop tasks well. But worse than that, they will be forcing the average consumer to learn how to interact with a third, awkward interface. I think it's safe to say that consumers are pretty lazy and dumb when it comes to learning a new interface for no good reason. Most humans (in developed countries, lets say) already know how to (basically) use Windows/Mac style PC's, and they also just finished learning how to use touch-based phone/tablet interfaces. I really doubt that very many people are keen on re-training on Apple's new mash-up OS, Android's different mash-up OS, LG's different mash-up OS, etc. I think Apple and Android should just learn from MS' painful Windows 8 debacle and copy the "final" solution that MS came up with...just have two very separate, but good interfaces available at the same time, and you decide. Tablet mode, for when it's appropriate, Desktop mode for when you need it. The reason the approach didn't work out for MS is because people don't want a full-blowtorch-level PC that just "happens to become" an app-less tablet...what they REALLY want is an app-laden cigarette-lighter-level OS (like iOS and Android), that CAN become a "passable" desktop experience only in those moments when you need it to. In other words, the Mobile-desktop priorities are reversed now. I think that if Apple were ever to release a very light, clam-shell laptop that ran a desktop-ized-version of iOS, but could switch back to "normal" iOS if you ever wished, then that would be a massive hit with Millennials. I also think Android "O" should have already come with this dual-OS installed, it is 2017 after all. Even if one never personally used or switched into the "desktop" mode, what harm would it do to have it available to those who COULD take advantage of it???? I think the main reason Google is holding back from doing this is because they are intent on scrapping Android altogether in favor of their one OS to rule them all, Fuchsia.

    • skane2600

      In reply to Jorge Garcia:

      Phone/Tablet vs Desktop is a false dichotomy We can have separate devices that can provide a much better than "passable" experience for each form-factor, and, in fact, we already do. Yes, the siren song of all-in-one devices and WORA is alluring, but the attempts have always failed and they always will.

  5. Narg

    I've been having a real problem with Android since "N". When my device is in Android Auto mode, of course from entering my vehicle with the phone out of my pocket, music will start playing to my settings. Great. Well, when I leave the vehicle of course the Bluetooth connection goes away, and Android Auto exits as expected. But, the music does not stop. This is annoying. I hope they figure that out.