Having to build only the add-on is also a great advantage that might save a lot of development time. Therefore, by using add-ons, OEMs can add libraries in their namespaces, providing functionalities that can be exported without infringing the CDD. According to the Android Compatibility Definition Document (CDD), OEMs are not allowed to change the Android public APIs - namely those in the protected namespaces: java.*, javax.*, sun.*, android.*, com.android.*. SDK Add-ons allow third-party actors to extend the Android SDK to add interfaces to their features without changing the Android SDK. The Android Software Development Kit (SDK) is a collection of libraries and tools that enables and makes it easier to develop Android applications. That’s when the SDK Add-on comes in handy. Whether you are an OEM company or a developer customising the Android Open Source Project, you might have come across the issue where you developed a feature and you would like for App developers to use it. How to build and use an Android SDK Add-on
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |