This codelab will teach you how to build a complication data provider.

Concepts and setup

At the end of the codelab, you will understand how to enable your data to appear in complications on Android Wear.

Concepts

To start off, let's learn a little bit about Complications. A complication is a feature of a watch face beyond hours and minutes. The unread message count and steps indicator are examples of complications seen in the image below.

The Complications API is for both watch faces and data provider apps. Let's look at the players:

In this code lab, we cover creating a complication data provider. If you are also interested in adding complications to your watch face, check out our other code lab, "Adding Complications to your Watch Face," after you are finished.

Let's get started!

Clone the starter project repo

To get started as quickly as possible, we have prepared a starter project for you to build on. It contains some basic code and application settings necessary for the code lab.

If you have Git installed, you can simply run the command below. (You can check if Git is installed by typing git --version in the terminal / command line and verify it executes correctly.)

 git clone https://github.com/googlecodelabs/data-providers.git

If you do not have Git, you can download the project as a zip file:

Download Zip

Import the project

Start Android Studio, and select "Open an existing Android Studio project" from the Welcome screen, open the project directory, and double-click on the build.gradle file in the ComplicationsDataProvider directory:

Click OK on "Import Project from Gradle" screen without making any changes. (You may see a screenshot like the one below.)

After the project has loaded, you may also see an alert like the one below, you can click "Ignore" or the "X" in the upper right. (You won't be pushing any changes back to the Git repo.)

In the upper-left corner of the project window, you should see something like the screenshot below if you are in the Android view. (If you are in the Project view, you will need to expand the ComplicationsDataProvider project to see the same thing.)

There are six folder icons. Each is a "module". Please note that Android Studio might take several seconds to compile the project in the background for the first time. During this time you will see a spinner in the status bar at the bottom of Android Studio:

We recommend that you wait until this has finished before making code changes. This will allow Android Studio to pull in all the necessary components. In addition, if you get a prompt saying "Reload for language changes to take effect?" or something similar, select "Yes".

Understand the starter project

All right, you're set up and ready to start exposing your data to complications. We'll set off using the 1-base module, which is the starting point for everything we'll be building upon. You will be adding code from each step to 1-base.

Each of the following modules can be used as reference points to check your work or for reference if you encounter any issues. The number in front of the module name corresponds with the codelab step.

Overview of key components

Emulator setup

If you need help setting up an Android Wear emulator, please refer to the "Set Up an Android Wear Emulator or Device" section of the "Creating and Running a Wearable App" article.

Run the starter project

Let's run it on a watch.

Waiting for device.
Target device: lge-urbane_2-XXXXXXXXXXXXXX
Uploading file
        local path: ~/Downloads/ComplicationsDataProvider /1-base/build/outputs/apk/1-base-debug.apk
        remote path: /data/local/tmp/com.example.android.wearable.complicationsdataprovider
Installing com.android.example.watchface
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.android.wearable.complicationsdataprovider"
pkg: /data/local/tmp/com.example.android.wearable.complicationsdataprovider
Success

Please note, since this is the first time you are running this watch face, you will need to select it from the favorites menu. After it has been selected once, it will show up as one of the options alongside this option.

Here's what it should look like. On some watches, the Elements Watch Face has complications enabled, so you might see populated complication on your watch. Don't worry if your emulator has a cloud with a strikethrough in place of the airplane icon. We will not need a connection to a phone / internet for this code lab.

Summary

In this step you've learned about:

Next up

Let's start exposing some data.

Code step 2

In this step, we will start exposing data. Complications accept several types of data. In this step, we will return the Short Text data type.

If at any point you are confused by the concepts discussed here, please refer to the "2-short-data" module and see how these steps may be implemented.

Specifying the data types your provider supports

Open the AndroidManifest.xml and look at the service CustomComplicationProviderService.

Notice the intent-filter:

<action android:name=
    "android.support.wearable.complications.ACTION_COMPLICATION_UPDATE_REQUEST"/>

This tells the system that your service extends ComplicationProviderService and can send data for complications.

Next is the meta-data element specifying the data type(s) you support. In this case, we support SMALL_IMAGE, but for this step, you will need to change that to SHORT_TEXT. Change your first meta-data element to read this:

<meta-data
    android:name="android.support.wearable.complications.SUPPORTED_TYPES"
    android:value="SHORT_TEXT"/>

Exposing your data

As stated earlier, onComplicationActivated() is called when your data provider is activated. This is a good place/time to perform any basic setup that needs to be done once per compilation.

However, onComplicationUpdate()is where the active complication will request updated data.

The method onComplicationUpdate() can be triggered for various reasons:

Open CustomComplicationProviderService.java and move down to the onComplicationUpdate() method. Copy and paste the code below under the initial Log.d() call.

// Used to create a unique key to use with SharedPreferences for this complication.
ComponentName thisProvider = new ComponentName(this, getClass());

// Retrieves your data, in this case, we grab an incrementing number from SharedPrefs.
SharedPreferences preferences =
       getSharedPreferences(
               ComplicationTapBroadcastReceiver.COMPLICATION_PROVIDER_PREFERENCES_FILE_KEY,
               0);
int number =
       preferences.getInt(
               ComplicationTapBroadcastReceiver.getPreferenceKey(
                       thisProvider, complicationId),
               0);
String numberText = String.format(Locale.getDefault(), "%d!", number);

In this case, we are getting a stored int in a SharedPreference that represents our data. This could easily be a call to your database.

We also convert it to a simple string in preparation to convert to a ComplicationData object.

Next we need to convert the data into a type the complication understands. In this case, we are converting it into the SHORT_TEXT data type.

A given data type may include different sets of fields. For example, SHORT_TEXT may be just a single piece of text, or a title and text, or an icon and text.

For our case, we are only setting the required field and none of the optional fields. To learn more about these types and fields, check out our documentation.

Copy and paste the code below under the new code you added earlier to retrieve our integer in the same method.

ComplicationData complicationData = null;

switch (dataType) {
   case ComplicationData.TYPE_SHORT_TEXT:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                       .setShortText(ComplicationText.plainText(numberText))
                       .build();
       break;
   default:
       if (Log.isLoggable(TAG, Log.WARN)) {
           Log.w(TAG, "Unexpected complication type " + dataType);
       }
}

You are probably wondering why we are using a switch to create the data. Later, we will want to support various forms of the data based on the type the system is requesting. By using a switch now, we can easily add new data types (LONG_TEXT, RANGED_VALUE, etc.) later with minimal work.

Finally, now that we have the data in the right format, we must send the new data to the system. Copy and paste the following code below the code above.

if (complicationData != null) {
   complicationManager.updateComplicationData(complicationId, complicationData);

} else {
   // If no data is sent, we still need to inform the ComplicationManager, so the update
   // job can finish and the wake lock isn't held any longer than necessary.
   complicationManager.noUpdateRequired(complicationId);
}

Your final method should look like this:

@Override
public void onComplicationUpdate(
       int complicationId, int dataType, ComplicationManager complicationManager) {

   Log.d(TAG, "onComplicationUpdate() id: " + complicationId);

   ComponentName thisProvider = new ComponentName(this, getClass());

   SharedPreferences preferences = getSharedPreferences( ComplicationTapBroadcastReceiver.COMPLICATION_PROVIDER_PREFERENCES_FILE_KEY, 0);

   int number =
           preferences.getInt(
                   ComplicationTapBroadcastReceiver.getPreferenceKey(
                           thisProvider, complicationId),
                   0);
   String numberText = String.format(Locale.getDefault(), "%d!", number);

   ComplicationData complicationData = null;

   switch (dataType) {
       case ComplicationData.TYPE_SHORT_TEXT:
           complicationData =
                   new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                           .setShortText(ComplicationText.plainText(numberText))
                           .build();
           break;
       default:
           if (Log.isLoggable(TAG, Log.WARN)) {
               Log.w(TAG, "Unexpected complication type " + dataType);
           }
   }

   if (complicationData != null) {
       complicationManager.updateComplicationData(complicationId, complicationData);

   } else {
       // If no data is sent, we still need to inform the ComplicationManager, so
       // the update job can finish and the wake lock isn't held any longer.
       complicationManager.noUpdateRequired(complicationId);
   }
}

Run the app again

In the first step, you learned how to install your complication data service on your device or emulator. Now it's time to do that again! Install your app and reselect the complication, i.e., swipe watchface, select gear, navigate to same complication, and select the Complications Data Provider Codelab. You should see something like this:

Summary

In this step you've learned:

Next up

Let's try supporting a different data type.

Code step 3

In this step, we will trigger updates in the data through the user tapping on our complication.

If at any point you are confused by the concepts discussed here, please refer to the "3-trigger-updates" module and see how these steps may be implemented.

Specifying how often the complication should refresh your data

Open the AndroidManifest.xml and look again at the service CustomComplicationProviderService.

You will notice an UPDATE_PERIOD_SECONDS field in the meta-data element. This specifies how often you want the system to check for updates to the data when your data provider is active.

Right now, it is set to 600 seconds (10 minutes). If you are using UPDATE_PERIOD_SECONDS, we recommend setting updates in order of minutes. Note that this value is only guidance for the system. Android Wear may update less frequently.

A better approach is a "push style" where we tell the system only when the data has changed.

Change the update frequency from 600 to 0, since we will be telling the system only when data has changed. Note, the meta-data is a requirement.

<meta-data 
    android:name="android.support.wearable.complications.UPDATE_PERIOD_SECONDS"
    android:value="0"/>

Informing the system that new complication data is available

Open ComplicationTapBroadcastReceiver.java. This BroadcastReceiver class updates our complication data when it's triggered. (Remember we are just saving the data to a SharedPreference.)

The class also offers several helper methods that construct a PendingIntent (triggers it as a BroadcastReceiver) and create unique preference keys for our complication (used with SharedPreference).

Right now, it only updates the integer in SharedPreference. We need to tell our complication that the data has been updated.

Move to the bottom of the onReceive() method. Copy and paste the code below the editor.apply() call.

// Request an update for the complication that has just been tapped.
ProviderUpdateRequester requester = new ProviderUpdateRequester(context, provider);
requester.requestUpdate(complicationId);

This instructs Android Wear that our complication's data has been updated. We need three pieces of data for this to work:

Ok, we are all done. Your final method should look like this:

@Override
public void onReceive(Context context, Intent intent) {
   Bundle extras = intent.getExtras();
   ComponentName provider = extras.getParcelable(EXTRA_PROVIDER_COMPONENT);
   int complicationId = extras.getInt(EXTRA_COMPLICATION_ID);

   // Retrieve data via SharedPreferences.
   String preferenceKey = getPreferenceKey(provider, complicationId);
   SharedPreferences sharedPreferences =
           context.getSharedPreferences(COMPLICATION_PROVIDER_PREFERENCES_FILE_KEY, 0);

   int value = sharedPreferences.getInt(preferenceKey, 0);

   // Update data for complication.
   value = (value + 1) % MAX_NUMBER;

   SharedPreferences.Editor editor = sharedPreferences.edit();
   editor.putInt(preferenceKey, value);
   editor.apply();

   // Request an update for the complication that has just been tapped.
   ProviderUpdateRequester requester = new ProviderUpdateRequester(context, provider);
   requester.requestUpdate(complicationId);
}

Adding a tap action to our complication

Now that our BroadcastReceiver not only updates the data but informs the system that new data is available (previous step), we need to add a tap action to our complication to trigger the BroadcastReceiver.

Open CustomComplicationProviderService.java and move down to the onComplicationUpdate() method.

Find this line of code (first couple lines of the onComplicationUpdate() method).

ComponentName thisProvider = new ComponentName(this, getClass());

Recall from the previous step that this was one of the pieces of data our BroadcastReceiver needed to inform the system that our complication had new data.

The other is the complication id which is passed into this method.

We now need to create a PendingIntent that passes both those values along an Extra.

Luckily, ComplicationTapBroadcastReceiver provides this as a helper method.

Copy and paste the code below under the line of code you found earlier.

// We pass the complication id, so we can only update the specific complication tapped.
PendingIntent complicationPendingIntent =
       ComplicationTapBroadcastReceiver.getToggleIntent(
               this, thisProvider, complicationId);

Next we need to assign the PendingIntent to the tap event for our complication.

Find the switch statement and replace the case for ComplicationData.TYPE_SHORT_TEXT with the code below.

case ComplicationData.TYPE_SHORT_TEXT:
   complicationData =
           new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                   .setShortText(ComplicationText.plainText(numberText))
                   .setTapAction(complicationPendingIntent)
                   .build();
   break;

This only adds one line, the .setTapAction() method which assigns our new PendingIntent to the tap action for the complication.

We are all done. Your final method should look like this:

@Override
public void onComplicationUpdate(
       int complicationId, int dataType, ComplicationManager complicationManager) {
   Log.d(TAG, "onComplicationUpdate() id: " + complicationId);

   // Create Tap Action so that the user can trigger an update by tapping the complication.
   ComponentName thisProvider = new ComponentName(this, getClass());

   // We pass the complication id, so we can only update the specific complication tapped.
   PendingIntent complicationPendingIntent =
           ComplicationTapBroadcastReceiver.getToggleIntent(
                   this, thisProvider, complicationId);

   // Retrieves your data, in this case, we grab an incrementing number from SharedPrefs.
   SharedPreferences preferences =
           getSharedPreferences(
                   ComplicationTapBroadcastReceiver.COMPLICATION_PROVIDER_PREFERENCES_FILE_KEY,
                   0);
   int number =
           preferences.getInt(
                   ComplicationTapBroadcastReceiver.getPreferenceKey(
                           thisProvider, complicationId),
                   0);
   String numberText = String.format(Locale.getDefault(), "%d!", number);

   ComplicationData complicationData = null;

   switch (dataType) {
       case ComplicationData.TYPE_SHORT_TEXT:
           complicationData =
                   new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                           .setShortText(ComplicationText.plainText(numberText))
                           .setTapAction(complicationPendingIntent)
                           .build();
           break;
       default:
           if (Log.isLoggable(TAG, Log.WARN)) {
               Log.w(TAG, "Unexpected complication type " + dataType);
           }
   }

   if (complicationData != null) {
       complicationManager.updateComplicationData(complicationId, complicationData);

   } else {
        // If no data is sent, we still need to inform the ComplicationManager,
        // so the update job can finish and the wake lock isn't held any longer
        // than necessary.
       complicationManager.noUpdateRequired(complicationId);
   }
}

Run the app again

Install your app and reselect the complication, i.e., swipe watchface, select gear, navigate to same complication, and select the Random Number provider. You should see the same thing as you saw before. However, now you can tap on the complication and the data will update.

Summary

In this step you've learned:

Next up

Let's try supporting a different data type.

Code step 4

While we expose our data to the complications, it might be nice to support more types of data, and to see what different data types look like in complications.

Specifying a different supported data type

Open the AndroidManifest.xml again and look at the declaration of the service CustomComplicationProviderService.

Change the meta-data element SUPPORTED_TYPES from SHORT_TEXT to LONG_TEXT. Your change should now look like this:

<meta-data
    android:name="android.support.wearable.complications.SUPPORTED_TYPES"
    android:value="LONG_TEXT"/>

Adding support for LONG TEXT

Open CustomComplicationProviderService.java, move down to the switch statement in onComplicationUpdate() method, and add the following code below the end of the TYPE_SHORT_TEXT case and above the default case.

case ComplicationData.TYPE_LONG_TEXT:
   complicationData =
           new ComplicationData.Builder(ComplicationData.TYPE_LONG_TEXT)
                   .setLongText(ComplicationText.plainText("Number: " + numberText))
                   .setTapAction(complicationPendingIntent)
                   .build();
   break;

The switch statement should now look something like this:

switch (dataType) {
   case ComplicationData.TYPE_SHORT_TEXT:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                       .setShortText(ComplicationText.plainText(numberText))
                       .setTapAction(complicationPendingIntent)
                       .build();
       break;
   case ComplicationData.TYPE_LONG_TEXT:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_LONG_TEXT)
                       .setLongText(ComplicationText.plainText("Number: " + numberText))
                       .setTapAction(complicationPendingIntent)
                       .build();
       break;
   default:
       if (Log.isLoggable(TAG, Log.WARN)) {
           Log.w(TAG, "Unexpected complication type " + dataType);
       }
}

You've probably noticed by now that we are simply repackaging the same data in a new format. Let's see how it looks.

How to check your progress and debug

Install your service, but this time choose the bottom slot complication before choosing your complication service provider:

You should now see something like the image below. Note that each complication is stored under a separate key, so you might see different values if you have set the complication in multiple locations:

Summary

In this step you've learned about:

Next up

We want to support one extra data type before putting it all together.

Code step 5

While we expose our data to the complications, let's continue exploring how to support more types of data.

Specifying a different supported data type

Open the AndroidManifest.xml again and take a look at the service CustomComplicationProviderService.

Change the meta-data element SUPPORTED_TYPES to RANGED_VALUE. Your change should should now look like this:

<meta-data
    android:name="android.support.wearable.complications.SUPPORTED_TYPES"
    android:value="RANGED_VALUE"/>

Adding support for RANGED VALUES

Open CustomComplicationProviderService.java, move down to the switch statement in the onComplicationUpdate() method, and add the code below the TYPE_LONG_TEXT case and above the default case.

case ComplicationData.TYPE_RANGED_VALUE:
   complicationData =
           new ComplicationData.Builder(ComplicationData.TYPE_RANGED_VALUE)
                   .setValue(number)
                   .setMinValue(0)
                   .setMaxValue(ComplicationTapBroadcastReceiver.MAX_NUMBER)
                   .setShortText(ComplicationText.plainText(numberText))
                   .setTapAction(complicationPendingIntent)
                   .build();
   break;

Your switch statement should now look like this:

switch (dataType) {
   case ComplicationData.TYPE_SHORT_TEXT:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_SHORT_TEXT)
                       .setShortText(ComplicationText.plainText(numberText))
                       .setTapAction(complicationPendingIntent)
                       .build();
       break;
   case ComplicationData.TYPE_LONG_TEXT:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_LONG_TEXT)
                       .setLongText(ComplicationText.plainText("Number: " + numberText))
                       .setTapAction(complicationPendingIntent)
                       .build();
       break;
   case ComplicationData.TYPE_RANGED_VALUE:
       complicationData =
               new ComplicationData.Builder(ComplicationData.TYPE_RANGED_VALUE)
                       .setValue(number)
                       .setMinValue(0)
                       .setMaxValue(ComplicationTapBroadcastReceiver.MAX_NUMBER)
                       .setShortText(ComplicationText.plainText(numberText))
                       .setTapAction(complicationPendingIntent)
                       .build();
       break;
   default:
       if (Log.isLoggable(TAG, Log.WARN)) {
           Log.w(TAG, "Unexpected complication type " + dataType);
       }
}

Again, we are just repackaging the same data in a new format. Let's see how it looks.

How to check your progress and debug

Install your service, and choose another location.

You should now see something like this:

You can see a radial circle around the number that highlights the equivalent of 5/20.

Summary

In this step you've learned about:

Next up

We wrap up the code lab by enabling all the data type variations.

Code step 6

Right now our complication data provider supports three variations of our data (RANGED_VALUE, SHORT_TEXT, and LONG_TEXT).

In this last step, we will inform the system we support all three.

Specifying multiple supported data types

Open the AndroidManifest.xml again and look at the service CustomComplicationProviderService.

Change the meta-data element SUPPORTED_TYPES to RANGED_VALUE,SHORT_TEXT,LONG_TEXT. Your change should now look like this:

<meta-data
    android:name="android.support.wearable.complications.SUPPORTED_TYPES"
    android:value="RANGED_VALUE,SHORT_TEXT,LONG_TEXT"/>

Check your progress

Install your service.

In this case, the watch face prefers the ranged data type over both the short and long types, but if this complication only supported the short text type, the data would still show up because it supports all three data types. Keep in mind the watch face itself specifies the data types that a complication supports, and the order of preference of those types.

Summary

In this step you've learned about:

There are many more data types you can support in complications (including small images, large images, and icons). Try to extend this code lab by implementing some of those types on your own.

For more details on developing complications for watch faces and creating complication data providers, visit Watch Face Complications

For more details about developing Android Wear watch faces, visit https://developer.android.com/training/wearables/watch-faces/index.html