Copyright 2015 All rights reserved. This material can't be published, transferred, copied or redistributed.
However, we might get a preview of Android O at the Google I/O 2017 in May this year. The developer preview is basically created to give developers the opportunity of how the latest Android build works with their apps. These are the changes that Google won't highlight, yet you might find them really useful.
Another pretty major change is called "background limits". This should allow a smartphone's battery life to be extended as there won't be a ton of apps that will continue to work in the background, even if they are not being used by the phone owner.
GoogleAnnounces its Next version of Android i.e "Android O". Google is introducing the concept of notification channels, which can group notifications into user-defined categories. It's an official solution to the checkbox options already offered by some developers, letting you precisely control the notification activity of any supporting app from Android's settings menu. But we have a pretty good idea of what to expect from the update, which is primarily focused on improving battery life and notifications, and making Android a little friendlier to use with keyboards. A snoozing function is in too, which gets rid of a notification for a period of time, and then shows it again. This means users will be able to see how many new notifications there are for each app just by looking at the home screen.
Other new Android O features include a picture-in-picture view on phones and tablets so you can keep watching a video while using other apps - like hailing a auto or answering a message. So that, but OS-wide. Supporting apps will allow their main content to be popped out into a sticky window that persists on the display above other apps.
Other features worth mentioning include a picture-in-picture mode for phones (the feature came to tablets last year), "adaptive" app icons that should look native to multiple phone launchers, better keyboard navigation for devices like Chromebooks and support for autofill apps.
Auto Fill APIs: Users can choose an "autofill" app similarly to how you now choose a default keyboard. This means your auto head unit's call and reject buttons will work with third-party apps (think VoIP) too. What are the issues that occur in terms of design guidelines and the new API's. The Android Runtime should be faster than ever before, with improvements of up to 2x.