Android fragmentation is a serious issue for users and developers, performing android apps development, across the world. With Android 7.0 one cannot expect to solve all the problems or issues. This is also a matter of prestige as it also possesses consistent performance improvements which users can avail of. While there are no major game-changers here, it is important to have a look at some of the important Android tweaks and the fresh opportunities they present.
New JIT Compiler, Profile-Guided Compilation:
The days of JIT compilation have returned. Google has now included a JIT compiler with code profiling to ART. This has been done to enhance ART's current AOT complier. ART establishes a profile for each application's hot methods and different device conditions. In advance, it can compile methods for optimal performance; bring down RAM usage and power consumption, etc.
With profile-guided compilation, developers can ensure high performance with efficiency. The process of installation and updating will speed up. With Google's profound documentation, understanding implementation would be a matter of some time. Time-saving for one and all!
Multi-window functionality may not be in much demand in the mobile field. However, with Google getting ready to launch Smart TV, this functionality might be useful. It might also be applicable for other devices like oversized phablets, tablets, and devices with big screen displays which will allow users to experiment with Window size and position.
With multi-window support, Android tablets and smart TVs can get picture-in-picture functionality. As Android TVs aren’t very popular, it is productivity apps that can get its benefits.
Vulkan API is a novel close-to-metal API meant for graphics processing units or GPUs. On multi-thread processors they must deliver high performance and support cross-platform compatibility. It brings down the number of man hours in driver-development. However, it will be slowly adopted because it is a very powerful and complex graphics API.
When an Android 7.0 device is locked, it runs in direct boot mode till the device is unlocked. For this, Android 7.0 possesses two storage locations for data with two unique encryption solutions.
Device encrypted storage: Can be accessed even if device is locked
Credential encrypted storage: Can be accessed when the device is unlocked.
Apps cannot run in direct boot. However, developers, involved in android apps development, can register various components of the app that need to run in direct boot mode.
With direct boot, one can expect improved security without having to adjust with user experience and responsiveness. This will include apps which deliver notifications. Apps that need access to storage will have to depend on device encrypted storage, which is sealed with a key which is available once a device undergoes boot verification.
This access is not for data related with user credentials such as PIN and passwords. Credential encrypted storage is accessible only after the device boots up and the user unlocks it. It is available till the device powers down.
In a nut shell, Android 7.0 is all about optimization. It is not a major benchmark which will transform the apps world. We are in times when rapid mobile hardware and software evolution's are the thing of the past. Incremental has now become commonplace.
With news of Google's decision to launch Pixel Phones to avail of Android 7.0 doing rounds, it is certain that Android 7.0 is not the OS in itself. However, how all this falls into place and transforms the mobile world is yet to be seen.