[Edit: Updated ship service on December 21 to clarify that when the 64-bit requirement is introduced inward August 2019, 32-bit back upwards is non going away. Apps that include a 32-bit library merely take away to guide hold a 64-bit version too.]
Google Play powers billions of app installs in addition to updates annually. We relentlessly focus on safety in addition to functioning to ensure everyone has a positive sense discovering in addition to installing apps in addition to games they love. Today we're giving Android developers a heads-up near 3 changes designed to back upwards these goals, equally good equally explaining the reasons for each change, in addition to how they volition assistance brand Android devices fifty-fifty to a greater extent than secure in addition to performant for the long term.
- In the minute one-half of 2018, Play volition require that novel apps in addition to app updates target a recent Android API level. This volition last required for novel apps inward August 2018, in addition to for updates to existing apps inward November 2018. This is to ensure apps are built on the latest APIs optimized for safety in addition to performance.
- In August 2019, Play volition require that novel apps in addition to app updates alongside native libraries supply 64-bit versions inward add-on to their 32-bit versions.
- Additionally, inward early on 2018, Play volition starting fourth dimension adding a small-scale total of safety metadata on pinnacle of each APK to farther verify app authenticity. You create non take away to accept whatever activity for this change.
We deeply appreciate our developer ecosystem, in addition to thence promise this long advance notice is helpful inward planning your app releases. We volition proceed to supply reminders in addition to portion developer resources equally cardinal dates approach to assistance y'all prepare.
Target API score requirement from belatedly 2018
API deportment changes advance the safety in addition to privacy protections of Android – helping developers secure their apps in addition to protecting people from malware. Here are a few such changes from recent platform versions:
- Implicit intents for bindService() no longer supported (Android 5.0)
- Runtime permissions (Android 6.0)
- User-added CAs non trusted yesteryear default for secure connections (Android 7.0)
- Apps can't access user accounts without explicit user blessing (Android 8.0)
Many of these changes exclusively apply to apps that explicitly declare their back upwards for novel API behaviors, through the targetSdkVersion manifest attribute. For example, exclusively apps alongside a targetSdkVersion of 23 (the API score of Android 6.0) or higher plow over the user total command over what someone information – such equally contacts or place – the app tin plow over the axe access via runtime permissions. Similarly, recent releases include user sense improvements that foreclose apps from accidentally overusing resources similar battery in addition to memory; background execution limits is a practiced instance of this type of improvement.
In guild to supply users alongside the best Android sense possible, the Google Play Console volition require that apps target a recent API level:
- August 2018: New apps required to target API score 26 (Android 8.0) or higher.
- November 2018: Updates to existing apps required to target API score 26 or higher.
- 2019 onwards: Each twelvemonth the
targetSdkVersionrequirement volition advance. Within ane twelvemonth next each Android dessert release, novel apps in addition to app updates volition take away to target the corresponding API score or higher.
Existing apps that are non receiving updates are unaffected. Developers rest gratis to usage a minSdkVersion of their choice, thence at that spot is no alter to your mightiness to cook apps for older Android versions. We encourage developers to supply backwards compatibility equally far equally reasonably possible. Future Android versions volition also trammel apps that don't target a recent API score in addition to adversely impact functioning or security. We desire to proactively cut back fragmentation inward the app ecosystem in addition to ensure apps are secure in addition to performant acre providing developers alongside a long window in addition to enough of notice inward guild to computer programme ahead.
This twelvemonth nosotros released Android Oreo, the most secure in addition to best performing version of Android yet, in addition to nosotros introduced Project Treble to assistance the latest releases range devices faster. Get started edifice apps that target Android 8.1 Oreo today.
64-bit back upwards requirement inward 2019
Platform back upwards for 64-bit architectures was introduced inward Android 5.0. Today, over 40% of Android devices coming online guide hold 64-bit support, acre all the same maintaining 32-bit compatibility. For apps that usage native libraries, 64-bit code typically offers significantly ameliorate performance, alongside additional registers in addition to novel instructions.
In anticipation of hereafter Android devices that back upwards 64-bit code only, the Play Console volition require that novel apps in addition to app updates alongside native libraries supply 64-bit versions inward add-on to their 32-bit versions. This tin plow over the axe last inside a unmarried APK or equally ane of the multiple APKs published.
We are non removing 32-bit support. Google Play volition proceed to back upwards 32-bit apps in addition to devices. Apps that create non include native code are unaffected.
This alter volition come upwards into number inward August 2019. We're providing advance notice today to let enough of fourth dimension for developers who don't yet back upwards 64-bit to computer programme the transition. Stay tuned for a hereafter ship service inward which we'll accept an in-depth await at the functioning benefits of 64-bit native libraries on Android, in addition to cheque out the CPUs in addition to Architectures guide of the NDK for to a greater extent than info.
Security metadata inward early on 2018
Next twelvemonth we'll laid about adding a small-scale total of safety metadata on pinnacle of each APK to verify that it was officially distributed yesteryear Google Play. Often when y'all purchase a physical product, you'll discovery an official label or a badge which signifies the product's authenticity. The metadata we're adding to APKs is similar a Play badge of authenticity for your Android app.
No activity is needed yesteryear developers or users. We'll accommodate Play's maximum APK size to accept into concern human relationship the small-scale metadata addition, which is inserted into the APK Signing Block in addition to does non alter the functionality of your app. In add-on to enhancing the integrity of Play's mobile app ecosystem, this metadata volition enable novel distribution opportunities for developers inward the hereafter in addition to assistance to a greater extent than people maintain their apps upwards to date.
Looking ahead
2017 has been a fantastic twelvemonth for developers who guide hold seen increase in addition to success on Google Play. We've been difficult at piece of occupation on features (including those announced at I/O 2017 in addition to at Playtime) to assistance y'all improve your app character in addition to concern performance. With these features in addition to the upcoming updates, nosotros promise to encounter the Android in addition to Play ecosystem proceed to thrive inward 2018 in addition to beyond.
How useful did y'all discovery this blogpost?
