We are most definitely only a few months clear of the primary developer preview unlock of Android P, however there are some hints of what Google‘s cooking in AOSP. In keeping with a document at XDA, Google may well be making plans a transfer that’ll dissatisfied some builders. New commits recommend Google will take away get entry to to unofficial APIs within the subsequent giant Android unlock.
Android has an excellent many APIs for builders to make use of, however there also are some hidden APIs that don’t seem to be technically a part of the SDK. Builders infrequently use those to permit complex options or as shortcuts, however they are able to purpose problems when Android updates roll out. Undocumented APIs can be used to have interaction in actions that negatively have an effect on device steadiness or efficiency, which is unhealthy for customers.
This devote used to be ultimately cut up into 3 smaller commits with the similar gist.
In response to the happenings in AOSP, Google would possibly block apps from having access to the categories, strategies, and fields marked with “@conceal” in AOSP. A brand new construct software known as hiddenapi modifies the get entry to flags of all signatures that seem on a black or graylist, making hidden APIs inaccessible to builders. Apps that attempt to use them on Android P would fail to paintings. That checklist would even be utilized in CTS to verify hidden APIs aren’t discoverable on a tool.
In some other devote, Google builders discuss including a device for suggesting choices to builders seeking to get entry to hidden APIs. None of that is set in stone but, and maximum builders the usage of hidden APIs do not abuse them. In maximum cases, builders will have to have the ability to in finding choices, however some apps would possibly by no means be the similar.