4 ms·

Why not use an older API version?

• izacus 8y ago
  Since 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 ago
    I'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 ago
      Yes, 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.
      • kevin_thibedeau 8y ago
        Nothing prohibits backporting Cyanogen/Lineage permission controls to previous releases.
    • j16sdiz 8y ago
      Not if you want to be listed on play store > As we announced last year, Google Play will require all app updates to target Android Oreo (targetSdkVersion 26 or higher) by November 2018. https://android-developers.googleblog.com/2018/08/introducing-android-9-pie.html https://android-developers.googleblog.com/2018/08/introducin...
      • distances 8y ago
        Target sdk is different from min sdk. The feature set you can use depends on min sdk.