Google May Restrict Access From Undocumented Apps With Hidden APIs In Android P '9'
While some Android developer are still thinking on what the next Android version will be named, although we already have suggested names. However, there are some absorbing developments going on behind-the-scenes.
According to XDA few note-worthy upcoming features in Android P "9" has been spotted. We're probably just a few months away from the first developer preview release of Android P, but there are some hints of what Google's cooking in AOSP. According to a report at XDA, Google might be planning a move that'll piss off some developers. New commits suggest Google will remove access to unofficial APIs in the next big Android release, which means that applications maybe restricted from accessing APIs that are undocumented/hidden in the Android SDK (i.e in Android P).
Android has a great many APIs for developers to use, but there are also some hidden APIs that aren't technically part of the SDK. Developers sometimes use these to enable advanced features or as shortcuts, but they can cause issues when Android updates roll out. Undocumented APIs can also be used to engage in activities that negatively impact system stability or performance, which is bad for users.
Based on the happenings in AOSP, Google might block apps from accessing the classes, methods, and fields marked with "@hide" in AOSP. A new build tool called hiddenapi modifies the access flags of all signatures that appear on a black or graylist, making hidden APIs inaccessible to developers. Apps that try to use them on Android P would fail to work. That list would also be used in CTS to ensure hidden APIs are not discoverable on a device.
Hence, the founder of Commonsware "Mark Murphy" agrees to Google's decision saying "I agree with the assessment that bulk-banning access to @hide-annotated items will be a big deal, if that comes to pass. Hopefully, few apps access these items as part of key functionality. However, I suspect that lots of name-brand apps use them on occasion, directly or through a library".
In another commit, Google developers talk about adding a system for suggesting alternatives to developers trying to access hidden APIs. None of this is set in stone yet, and most developers using hidden APIs don't abuse them. In most instances, developers should be able to find alternatives, but some apps might never be the same.
According to XDA few note-worthy upcoming features in Android P "9" has been spotted. We're probably just a few months away from the first developer preview release of Android P, but there are some hints of what Google's cooking in AOSP. According to a report at XDA, Google might be planning a move that'll piss off some developers. New commits suggest Google will remove access to unofficial APIs in the next big Android release, which means that applications maybe restricted from accessing APIs that are undocumented/hidden in the Android SDK (i.e in Android P).
Android has a great many APIs for developers to use, but there are also some hidden APIs that aren't technically part of the SDK. Developers sometimes use these to enable advanced features or as shortcuts, but they can cause issues when Android updates roll out. Undocumented APIs can also be used to engage in activities that negatively impact system stability or performance, which is bad for users.
Based on the happenings in AOSP, Google might block apps from accessing the classes, methods, and fields marked with "@hide" in AOSP. A new build tool called hiddenapi modifies the access flags of all signatures that appear on a black or graylist, making hidden APIs inaccessible to developers. Apps that try to use them on Android P would fail to work. That list would also be used in CTS to ensure hidden APIs are not discoverable on a device.
Hence, the founder of Commonsware "Mark Murphy" agrees to Google's decision saying "I agree with the assessment that bulk-banning access to @hide-annotated items will be a big deal, if that comes to pass. Hopefully, few apps access these items as part of key functionality. However, I suspect that lots of name-brand apps use them on occasion, directly or through a library".
In another commit, Google developers talk about adding a system for suggesting alternatives to developers trying to access hidden APIs. None of this is set in stone yet, and most developers using hidden APIs don't abuse them. In most instances, developers should be able to find alternatives, but some apps might never be the same.