3 ms·

What are you upgrading? Usually it's just a matter of changing a couple numbers in the Gradle file. The only headache with new SDKs are if you're trying to inte

What are you upgrading? Usually it's just a matter of changing a couple numbers in the Gradle file. The only headache with new SDKs are if you're trying to integrate new features that aren't in appcompat but even then it's straight forward to support.

ilove_banh_mi 8y ago
Mainly notifications and speech.
0x0 8y ago
There's been tons of subtle and not so subtle breaking changes from bumping targetSdkVersion, many that only manifests at runtime. Things like runtime-permission-grants, three iterations of C2DM, GCM, FCM, notification handling, inner classes in activities and fragments, background processing, NDK changes, etc etc. If you have a low-churn legacy but still useful app, coming back every year and between the subtle api changes (which require runtime testing on old and new android devices) combined with an ever-reorganized google api console and play store console and firebase console is quite an effort. But I guess that's the cost of playing in the play store and for progress in the mobile OS landscape.
- j16sdiz 8y ago
  GCM is being removed by google. You have to migrate to FCM anyway. This is unrelated to the targetSdkVersion.
  - oakesm9 8y ago
    And it's a very small change on the app side to make the switch. It's essentially the same service but rebranded.