Watch Face Complication Provider

The watch face complication provider application is a service application to provide complication data. Complication provider application provides only data. The watch face application decides how to display the complications. The complication provider application provides the complication data by using the watch face complication provider API to the watch face application.


To enable your application to use the watch face complication functionality:

  1. To use the Watch Face Complication API to communicate with the watch face application, this application has to request permission by adding the following privilege to the tizen-manifest.xml file:

  2. To use the functions and data types for the Watch Face Complication Provider API, include the <watchface-complication-provider.h> header file in your application:
    #include <watchface-complication-provider.h>

Updating Complication Data

When the request occurs to update the complication data, the complication provider application can receive the request by adding watchface_complication_provider_update_requested_cb(). The watch face application can send the update request, and this request also occurs after the complication provider application notifies that the complication data is changed.

void _watchface_complication_provider_update_requested_cb(const char *provider_id,
		const char *req_appid, watchface_complication_type_e type, const bundle *context,
		bundle *share_data, void *user_data)

bool app_create(void *data)
			_watchface_complication_provider_update_requested_cb, NULL);

The complication provider application must set the updated complication data to shared_data in the update requested callback. And it is possible to verify whether the data is valid or not using watchface_complication_provider_data_is_valid(). If the data is invalid, watchface_complication_updated_cb() of the complication will not be called.

The complication data can be set using the following APIs. These APIs can be used only in watchface_complication_provider_update_requested_cb():

API Description
watchface_complication_provider_data_set_title() Set the complication title.
watchface_complication_provider_data_set_short_text() Set the short text type data.
watchface_complication_provider_data_set_long_text() Set the long text type data.
watchface_complication_provider_data_set_image_path() Set the image path type data.
watchface_complication_provider_data_set_ranged_value() Set the ranged value type data.
watchface_complication_provider_data_set_icon_path() Set the icon path type data.
watchface_complication_provider_data_set_timestamp() Set the timestamp type data.
watchface_complication_provider_data_set_extra_data() Set the extra data.
void _watchface_complication_provider_update_requested_cb(const char *provider_id,
		const char *req_appid, watchface_complication_type_e type, const bundle *context,
		bundle *share_data, void *user_data)
	bool is_valid;

		watchface_complication_provider_data_set_short_text(shared_data, "updated short text");

		watchface_complication_provider_data_is_valid(shared_data, &is_valid);

If the callback is not necessary, it can be removed by using watchface_complication_provider_remove_update_requested_cb():


Notifying the Complication Data Update

When the complication data is changed, the complication provider application can notify that the complication data is updated. If the notification successfully transfers to the complication, the complication data update request will occur:


Transferring Event Action

The complication provider can provide additional action that is touching. In this case, complication provider is launched with touch event and information of provider that has touched.

The following are event types:

Event type Description
WATCHFACE_COMPLICATION_EVENT_NONE The complication is not tapped.
WATCHFACE_COMPLICATION_EVENT_TAP The complication is tapped.
WATCHFACE_COMPLICATION_EVENT_DOUBLE_TAP The compliation is double tapped.

The complication provider provides followings:

  1. The complication provider can set the support events in tizen-manifest.xml using <support-event>.
  2. The complication provider can get the transferred event from app_control_h that is the parameter of the app_control life cycle callback by using watchface_complication_provider_get_event(). And if the touch event is transferred from watchface, the information of the complication is also transferred.

    To get the information, the following functions are used to get the information:

    API Information
    watchface_complication_provider_event_get_provider_id() Gets the provider id of touched complication.
    watchface_complication_provider_event_launch_get_complication_type() Gets the complication type of touched complication.
    watchface_complication_provider_event_launch_get_context() Gets the context information of touched complication.

    Then Complication provider can define the action according to the event and the information of complication that is touched.

    void app_control(app_control_h app_control, void *data)
            watchface_complication_event_type_e event_type;
            char *provider_id;
            watchface_complication_type_e type;
            bundle *context;
            watchface_complication_provider_get_event(app_control, &event_type);
            if (event_type == WATCHFACE_COMPLICATION_EVENT_TAP) {
                            app_control, &type);
                    /* Do something */

Providing XML Schema to Create Complication Provider Application

To create the complication provider application, complication provider tags are provided in tizen-manifest.xml file. It is possible to provide multiple complication provider in a complication provider application:

<complication provider-id="mycomplicationid" setup-appid="org.tizen.watch_setting">

It is mandatory to use attribute provider-id that is the id of the complication. If it is necessary to set the options to provide the specific data (such as, world clock), it can provide the complication setting application. In this case, setup-appid is the appid of the complication setting application.

If the trusted attribute value is true, the complication provider do not send data to the complications which have different certificate.

At least one <support-type> is necessary to create the complication provider application. Also, it is possible to support multiple types. These support type means data type and the complication provider provides data types that are defined in xml. It is not possible to declare duplicated data type for one complication provider id.


And, the specific default value is mandatory depending on each support types:

Support types Mandatory default values Optional default values
<short-text-type> <default-short-text> <default-title>
<long-text-type> <default-long-text> <default-title>
<ranged-value-type> <default-value> <default-title>
  <default-min> <default-short-text>
  <default-max> <default-icon>
<icon-type> <default-icon> <default-extra-data>
<image-type> <default-image> <default-extra-data>
<time-type> <default-hour> <default-short-text>
  <default-minute> <default-extra-data>

<label> is the name of the complication provider. If it is necessary to support the multiple language, multiple language tag must be provided:

<label xml:lang="en-us">EngComplication</label>

<period> is used to update complication provider data automatically, and in unit seconds:


In this case, the complication will send data update request to the complication provider every 60 seconds.

<support-event> is the type of event that can be supported. It is possible to set tap, double-tap events or both.

And it is possible to add <privileges> to restrict getting the complication data. In this case, watchface must add the specific privileges to get the complication data in tizen-manifext.xml:

<complication provider-id="mycomplicationid" setup-appid ="org.tizen.watch_setting" trusted="true">
	<label xml:lang="en-us">EngLabel</label>