The OneDrive Picker Android SDK by OneDrive communicates with the Java APIs, allowing to implement cloud features into Android applications. Authentication is not required to handle. Also, developers don't need to create their own thumbnails, because OneDrive permits to choose from the video and images of the users' files.
Most enterprise IT environments consist of multiple generations of legacy enterprise applications that collectively represent a business process. In recent years, the more advanced IT organizations have layered suites of business process management (BPM) software as part of an effort to manage those business processes in a more holistic fashion.
Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?