10 ms·
Android Pie SDK is now more Kotlin-friendly
- drb91 8y agoI really wish they used version numbers rather than names so i can tell there’s a new version of android. I thought this was a just a distro for raspberry pis. It’s pretty clear in the article though, no sweat :)
- amitutk 8y agoThere is a version letter, P in this case. The last version being O(reo).
- simcop2387 8y agoThey sort of do, the first letter of the new name is always the next one in the english alphabet. That said, they do have version numbers but almost no marketing uses them with or instead of the codenames. Kitkat Lolipop Marshmallow https://en.wikipedia.org/wiki/Android_version_history https://en.wikipedia.org/wiki/Android_version_history
- the_trapper 8y agoThe stupid thing is that these code names sometimes span multiple versions of Android and even API levels making it all even more of a clusterfuck of a platform. My suspicion is that they do this to hide all of the fragmentation and pretend that more handsets are up to date than they actually are.
- altair8800 8y agoWhat's the difference between named releases and Apple's semantic versioning? Both create groupings that hide fragmentation.
- sjwright 8y agoWhat fragmentation is being hidden behind Apple's iOS version numbers?
- altair8800 8y agoI should have said can hide fragmentation.
- mikelward 8y agoThe major "dessert" releases seem to happen about once a year now, with a big marketing push, and often substantial user-visible changes. API levels change when there are major developer-visible changes. I assume any time there's a backwards incompatible change for app developers, they bump the API version, as is standard for any API. No conspiracy theory required.
- wyattpeak 8y agoFunnily, I've been using Android for years and I never noticed until I thought "Why on earth would they call it Pie?" and it struck me. Guess I'm not as observant as I think.
- izacus 8y agoFor app developers, the API level (which is 28 for Android 9.0 / Pie) is significantly more relevant, since it determines API breakages, behaviour changes and backwards compatibility.
- cryptos 8y agoI hate this with Ubuntu, too. And then you see that you systems since <crazy name> are supported and you have to google to find out the actual Ubuntu release number and compare it to that of the target system. Annoying!
- ilove_banh_mi 8y agoI'm giving up on upgrading my apps for Android. The releases are dividing the market every single year and consequently steadily eroding sales. On the one hand Google's Nexus was released 3 years ago and is now obsolete; on the other hand Apple's iPhone 5s was released 5 years ago and gets to run iOS 12. On top of this, the vast majority of my paying customers use iOS, not Android (a variety of lifestyle and reference apps). This is disappointing; I can't financially justify further development for Android. Oreo, released in 2017, is at a pitiful 12% installation share. [1] [1] https://developer.android.com/about/dashboards/ https://developer.android.com/about/dashboards/
- jdc 8y agoWhy not use an older API version?
- izacus 8y agoSince this year you won't be allowed to do that anymore - since backwards compatibility behaviour allowed app developers to avoid privacy protecting features like runtime permissions.
- skybrian 8y agoI'm not an Android developer but they say supporting older versions should still work: "Existing apps that are not receiving updates are unaffected. Developers remain free to use a minSdkVersion of their choice, so there is no change to your ability to build apps for older Android versions." [1] https://developer.android.com/distribute/best-practices/develop/target-sdk https://developer.android.com/distribute/best-practices/deve...
- fmorel 8y agoYes, you can still support older versions. But the app must target at least Oreo, which means supporting the new permission model on newer versions of Android while making use of unfettered access on older versions.
- izacus 8y agoIt's rather sad to see how none of the comments here are actually commenting on Android P/Kotlin friendliness. (Which is available to all Android developers, not only those targeting P - the nullability headers will give you all the benefits even if your app supports older Androids.)
- akerro 8y agoI actually wish there was an Android release targeted for Dart support with more Dart promotion. Since this year Java got a lot more powers, they're moving the language and ecosystem much faster, functional targets for Java 12 (will be released in 2019) contain almost everything Kotlin has now.
- weitzj 8y agoBut then it depends how much is dependent on changes on the JVM and how much will get into the Android VM. This nice thing of Kotlin is that you get a nice language which is JVM 6 compatible and thus supported on most Android platforms. The last information I have from Android is that you can use partially features from Java7/JVM7 but not all of them.
- wastedhours 8y agoYeah, I was expecting to see Dart given more prominence, but guessing the momentum Kotlin has and the comparative ease of moving that way from pure Java, the timings still aren't working out. Am only tinkering at the moment, but my excitement for Flutter means any push in the Dart direction is good for me.
- jillesvangurp 8y agoGiven the legal wrangling with Oracle, I don't think they will be eager to support Java. However, Kotlin has a native compiler (llvm based) as well. You can target Android/IOS with it as well as Wasm or simple desktop/server executables. So, the smart move would be to deemphasize Dart, move flutter on top of Kotlin native/llvm (and why not expose it to other languages as well; e.g. swift). Then they cab move the entire Android ecosystem on top of llvm and provide some level of continuity for people with Kotlin/Android codebases. The main challenge here is the API gap between the old java 6 APIs that underly the current Android API that won't be there on native Kotlin. Flutter solves that problem.
- sidlls 8y agoI get why developers would be interested in this, but it doesn't feel like something that moves the needle. It's a decent first step if the end goal is to promote Kotlin to the place Java occupies in Android development and (at the same time) fix some of the issues with the inconsistent and over-engineered APIs.