First Preview of Android N: Developer APIs and Tools
android-developers.blogspot.com
First Preview of Android N: Developer APIs and Tools
1–10 of 74 posts
Re: First Preview of Android N: Developer APIs and Tools
#2Re: First Preview of Android N: Developer APIs and Tools
#3>Improved Java 8 language support - We’re excited to bring Java 8 language features to Android. With Android's Jack compiler, you can now use many popular Java 8 language features, including lambdas and more, on Android versions as far back as Gingerbread. The new features help reduce boilerplate code. For example, lambdas can replace anonymous inner classes when providing event listeners. Some Java 8 language features --like default and static methods, streams, and functional interfaces -- are also now available on N and above. With Jack, we’re looking forward to tracking the Java language more closely while maintaining backward compatibility.
Re: First Preview of Android N: Developer APIs and Tools
#4Re: First Preview of Android N: Developer APIs and Tools
#5Re: First Preview of Android N: Developer APIs and Tools
#6ART will recompile applications based on profiling data.
Introduction of support to hardware keystores, with the mention that one use case is to prevent jailbreaking.
Prevent the NDK users that ignored the documentation and linked to non official platform libraries to keep doing that.
Re: First Preview of Android N: Developer APIs and Tools
#7I'm just a hobby developer, but the last four-ish months have been really exciting. There's a been ton released and polished in the developer console alone.
Re: First Preview of Android N: Developer APIs and Tools
#8Besides finally saying something about Java support, I found other items interesting. ART will recompile applications based on profiling data. Introduction of support to hardware keystores, with the mention that one use case is to prevent jailbreaking. Prevent the NDK users that ignored the documentation and linked to non official platform libraries to keep doing that.
They went back to having a JIT in addition to AOT - which means there is no AOT when the app is installed. When the device is idle/charging then AOT will selectively precompile the used portions of the app and optimize it further using the profiling data. So faster app installs (boon for FDE devices with slow NAND write speeds) and no optimizing apps step after system update.
Re: First Preview of Android N: Developer APIs and Tools
#9I guess I'll take a look at the APIs in 5 years, when it has enough market share to be worth considering.
Jelly Bean still has 30% market share, but are owners of 4 year old phones a significant portion of app revenue? I'd wager the people spending money have at least KitKat.
Lollipop, at a year and half old, has another 30%
Re: First Preview of Android N: Developer APIs and Tools
#10I guess I'll take a look at the APIs in 5 years, when it has enough market share to be worth considering.
Ice Cream Sandwich, which is 5 years old, has about vanished. Jelly Bean still has 30% market share, but are owners of 4 year old phones a significant portion of app revenue? I'd wager the people spending money have at least KitKat. Lollipop, at a year and half old, has another 30%
Digital Signage platforms especially (the part of the Android market I actually care about) seem to be largely stuck on 4.1.