Content Management SDK for Java & Android

Published

December 15, 2014

Author

Setup

The binaries for the library are published via Maven Central, and can be added to your project in several ways, depending on how you usually build your project.

Maven

Gradle

The latest version number and more details are available in the Setup section of the project's README file.

Creating a client

The CMAClient class manages all your interaction with the Management API. Every client is associated with an access token, which can be obtained through the management API documentation.

Creating a client is as simple as:

There are also several optional settings that can be specified through the client builder:

setLogLevel() - Configures a custom log level for the client. This can be useful for debugging purposes, as it outputs the network traffic according to the provided log level.

setClient() or setClientProvider() - Configures a custom HTTP client to carry the network requests.

Examples

Creating an entry:

Updating an entry:

Demo

Next we will demonstrate basic usage of the SDK from the context of an Android Wear project. For that, we have published the [Cookies Demo Application for Android][9].

Implementation

As you probably know, Android Wear applications normally require two projects - one that would run on the handheld device and another for the wearable side. Hence, the demo project is structured as follows:

ROOT FOLDER .. mobile/ -- Application module for handheld device .. wear/ -- Application module for wearable device .. shared/ -- Library project shared between both modules

The demo app makes use of the CMA SDK in order to create and publish entries. The CDA SDK is used for fetching random entries from the same Space.

The wearable project's MainActivity class has a layout consisting of two buttons. One for requesting a fortune cookie via the Delivery API and the other for storing new fortune cookies via the Management API. The text for the new fortune cookie will be retrieved from the user by voice, using an ACTION_RECOGNIZE_SPEECH Intent.

Since network operations should be performed by the handheld device, once one of the buttons is clicked, we deliver a message to the handheld device via the Wearable MessageApi. The message will be intercepted by a custom WearableListenerService, which in turn fetches or creates a fortune cookie according to the desired action. The result will be sent back to the wearable device by using the same mechanism.

In order to send a message from one side to the other (i.e. from the wearable to the handheld), we create a GoogleApiClient. Once the client is connected and ready, we should be able to send messages. A message consists of a path and an optional payload. We have declared the following method (from Utils.java) to send a message to other connected nodes:

Note that since we are using the synchronous versions of the getConnectedNodes() and sendMessage() methods, we spawn a new thread in order keep the main thread free.

On the handheld side, we have a custom WearableListenerService which intercepts these messages and delegates the work to an IntentService named CookieService. The following method will be invoked on a background thread when receiving a message for creating a new fortune cookie:

Here we simply create and publish a new Entry with our pre-defined Content Type and set it's **text** field value. If the operation was successful, we notify the wearable by firing yet another message. In case the operation has failed for any reason (i.e. network error), we fire a message with the error description.

On the wearable side, we have a custom **WearableListenerService** which intercepts these message and reacts accordingly:

Conclusion

If you haven't had a chance to develop for Android wear yet, hopefully this would show you how to start. The full source code for the demo app is available on GitHub. If you have any feedback about the SDK, feel free to communicate it through the GitHub repository.

Happy coding q:)