![]() If you need new APIs for your apps to take advantage of the DPC capabilities, please feel free to create an issue to describe your app and its use case of those APIs. If you are interested in improving the functionality of Island, please create an issue first to discuss your thoughts with us, we are open to collaboration in future development. If you found bugs, made minor improvements or translated the strings, please feel free to send us pull-requests. The protocol of all APIs are well defined and maintained in the class "Api". Developers can start building apps now to take advantage of the Island open APIs. Starting from the first public version of Island, all APIs are open to 3rd-party apps with the standard runtime-permission of Android as user authorization. Island itself will not focus on the rich set of features, but mainly focuses on building a powerful engine as an open platform for much more apps from the community. Island is devoted to build an open collaboration for community developers, either in development of this project or opening DPC capabilities to 3rd-party apps via open API. To encourage active exploration and broader development in the capabilities of DPC and therefore better benefit users, Open APIĭue to the exclusivity nature, user could only use one Android DPC app at a time, and price of switching DPC is far too heavy. ![]() The "mobile" and other modules can be installed and updated separately alongside "engine" module for development convenience. The "engine" module shares the same package name with the "complete" build, to inherit the profile/device owner privilege. ![]() To support separate "light" build for core modules, in the form of "product flavor" in Gradle build configuration. ![]() This project is constructed into several modules, with assembly module as the build portal, ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |