create your first tizen wearable native watch application welcome to tizen wearable native watch application development! note for watch face developers : you can create watch faces with galaxy watch studio or tizen studio for your personal enjoyment. however you will not be able to add watch face applications to seller portal until you have received approval to publish watch faces. the review is not required for watch app and widget developers. galaxy store supports watch faces for galaxy watch3 and earlier (samsung watches running on tizen). watch faces for galaxy watch4 and later (running on wear os powered by samsung) is only supported in the chinese galaxy store. a wearable native watch application is created using the c language, and can be run on tizen wearable devices to display a customized watch face to the user. study the following instructions to help familiarize yourself with the tizen native application development process as well as using the tizen studio and installing the created application on the emulator or target device. with the instructions, you can create and run a basic wearable native watch application, which displays some text and the current time on the screen: before you get started with developing tizen applications, download and install the tizen studio. for more information on the installation process, see the installation guide. create a wearable native watch project using the tizen studio. this step shows how you can use a predesigned project template that creates all the basic files and folders required for your project. build the application. after you have implemented code for the features you want, this step shows how you can build the application to validate and compile the code. run the application. this step shows how you can run the application on the emulator or a real target device. design a ui. this step shows how you can create the application ui and make small alterations to it to improve the usability of your application. when you are developing a more complex application, you can take advantage of the native tools included in the tizen studio to ease the tasks of creating functionality and designing the application ui. creating a project the following example shows you how to create and configure a basic wearable native watch application project in the tizen studio. an application project contains all the files that make up an application. the following figure illustrates the application to be created. the application screen displays the hello watch text and the current time, which continues to be refreshed every second while the application runs. figure: wearable native watch application to create the application project: launch the tizen studio. in the tizen studio menu, select file > new > tizen project. the project wizard opens. in the project wizard, define the project details. the project wizard is used to create the basic application skeleton with the required folder structure and mandatory files. you can easily create different applications by selecting an applicable template or sample for the project wizard to use. select the template project type and click next. select the profile (wearable) and version from a drop-down list and click next. the version depends on the platform version you have installed and with which you are developing the application. select the native application application type and click next. select the watch template and click next. define the project properties and click finish. you can enter the project name (3-50 characters) and the unique package id. you can also select the location and working sets by clicking more properties. the project wizard sets up the project, creates the application files using the default content from the template, and closes. for more information on the project wizard and the available templates, see creating tizen projects with tizen project wizard. you can see the created project in the project explorer view. the most important files and folders include: inc: default folder for included source files res: folder for resource files used by the application only shared: folder for resource files to be shared with other applications src: folder for source code files lib: folder for external library files tizen-manifest.xml: manifest file used by the platform to install and launch the application figure: application in the project explorer note : you can view and modify the application configuration in the manifest editor. in this example, no configuration changes are required. your application project is now ready for further actions. next, build the application. managing the application configuration to view and modify the application configuration: in the project explorer view, double-click the tizen-manifest.xml file of the application. the tizen studio opens the file in the manifest editor. in the manifest editor, view and modify the configuration details using the various tabs: overview: define general information, such as the package, label, and icon of the application. features: define required software and hardware features. this information is used for application filtering in the tizen store. privileges: define the security-sensitive apis or api groups accessed and used by the application. localization: define localized values for the application label, description, and icon. advanced: define advanced features, such as application metadata and some miscellaneous options. source: view and edit the source code of the tizen-manifest.xml file. changes made and saved on the other tabs are reflected in the source code and vice versa. note : the tizen-manifest.xml file must conform to both the xml file format and the tizen native application specification requirements. editing the file in the source tab is intended for advanced users only. to save any changes, in the tizen studio menu, select file > save all. for more information on configuring the application, see setting the application manifest. understanding the source code pay attention to the following main issues in the application source code (in the inc/watch.h and src/watch.c files), to understand how the application is designed and how it works. for source code details related to the ui, see designing a simple ui. the watch application is initialized to use the functions and data types of the watch application api by including the <watch_app.h> header file in your application: #include <watch_app.h> all header files that you need are already included in the watch.h file, which is generated by the tizen studio when the template project is created. the life-cycle callbacks manage specific parts of the application life-cycle. they are set in the watch_app_lifecycle_callback_s structure, and the structure is passed to the watch_app_main() function of the watch application api to start the watch application event loop: int main(int argc, char *argv[]) { appdata_s ad = {0,}; int ret = 0; watch_app_lifecycle_callback_s event_callback = {0,}; app_event_handler_h handlers[5] = {null,}; event_callback.create = app_create; event_callback.terminate = app_terminate; event_callback.pause = app_pause; event_callback.resume = app_resume; event_callback.app_control = app_control; event_callback.time_tick = app_time_tick; event_callback.ambient_tick = app_ambient_tick; event_callback.ambient_changed = app_ambient_changed; ret = watch_app_main(argc, argv, &event_callback, &ad); if (ret != app_error_none) dlog_print(dlog_error, log_tag, "watch_app_main() is failed. err = %d", ret); return ret; } the create event is triggered before the application main loop starts. in this callback, you can initialize the application resources, such as create windows and data structures. static bool app_create(int width, int height, void *data) { /* hook to take necessary actions before the main event loop starts initialize ui resources and application's data if this function returns true, the main loop of application starts if this function returns false, the application is terminated */ appdata_s *ad = data; create_base_gui(ad, width, height); return true; } the time_tick event is triggered at least once per second. the watch applications can get the current time from the watch_time time handle to draw a normal watch. static void app_time_tick(watch_time_h watch_time, void *data) { /* called each second while your app is visible; update the watch ui */ appdata_s *ad = data; update_watch(ad, watch_time, 0); } note : for more information on the application life-cycle callbacks, see applications. an ambient mode is available on a low-powered wearable device. in this mode, the watch application shows a limited ui and receives only the ambient tick event every minute to reduce power consumption. the details of the limited ui drawn in the ambient mode depend on the device. in addition, due to the ambient mode being a low power mode, there are limits to the colors that can be shown on the screen. usually, when designing the ambient mode ui, draw it with limited colors (cyan, magenta, yellow, red, green, blue, black and white), and use less than 15% of the pixels on the screen. if you do not want to draw your own ambient mode ui, set the ambient-support attribute to false in the watch application manifest file to allow the platform to show a default ambient mode ui. note : to use the ambient mode, the user must enable it in the device settings. in addition, on the galaxy watch device, the ambient mode activates only when you are wearing the watch on the wrist. - the `ambient_tick` callback is triggered every minute while the device is in the ambient mode. you can use the callback to update the time on your watch application in the ambient mode. in this callback, do not perform time-consuming tasks and always update the ui as quickly as possible. the platform can put the device to sleep shortly after the ambient tick expires. ```c static void app_ambient_tick(watch_time_h watch_time, void *data) { /* called at each minute while the device is in ambient mode. update watch ui. */ appdata_s *ad = data; update_watch(ad, watch_time, 1); } ``` - the `ambient_changed` callback is triggered when the ambient mode is enabled or disabled on the device. you can use the callback to initialize your ambient mode ui. ```c static void app_ambient_changed(bool ambient_mode, void *data) { if (ambient_mode) /* prepare to enter the ambient mode */ else /* prepare to exit the ambient mode */ } ``` building your application after you have created the application project, you can implement the required features. in this example, only the default features from the project template are used, and no code changes are required. when your application code is ready, you must build the application. the building process performs a validation check and compiles your files. you can build the application in the following ways: automatically the automatic build means that the tizen studio automatically rebuilds the application whenever you change a source or resource file and save the application project. to use the automatic build: select the project in the project explorer view. in the tizen studio menu, select project > build automatically. a check mark appears next to the menu option. you can toggle the automatic build on and off by reselecting project > build automatically. manually the manual build means that you determine yourself when the application is built. to manually build the application, right-click the project in the project explorer view and select build project. figure: manually building the application alternatively, you can also select the project in the project explorer view and do one of the following: in the tizen studio menu, select project > build project. press the f10 key. you can have more than one build configuration. to see the current active configuration or change it, right-click the project in the project explorer view and select build configurations > set active. the default configuration is debug. for more information, see building applications. after you have built the application, run it. running your application you can run the application on the emulator or a real target device. running on the emulator to run the application on the emulator: launch an emulator instance in the emulator manager: in the tizen studio menu, select tools > emulator manager. in the emulator manager, select a wearable emulator from the list and click launch. if no applicable emulator instance exists, create a new one. the emulator is launched in its own window. you can also see the new emulator instance and its folder structure in the device manager. generate a security profile. before you run the application, you must sign your application package with a certificate profile in the tizen studio. run the application: in the project explorer view, right-click the project and select run as > tizen native application. alternatively, you can also select the project in the project explorer view and do one of the following: press the ctrl + f11 key. click the run icon in the toolbar. if you have created multiple emulator instances, select the instance you want from the combo box in the toolbar before selecting to run the application. if you select an offline emulator, it is automatically launched when you select to run the application. confirm that the application launches on the emulator. note : if the emulator display has switched off, you cannot see the application launch. to switch the display on, click the power key (in the lower-right corner of the emulator). 3. change the watch face.<a name="watchface"></a> to change the watch face and make the installed watch application visible:  1. if the emulator display has been switched off, activate it by pressing the **power** key (in the lower-right corner of the emulator). 2. on the home screen (showing the default watch face), press the **power** key. 3. in the recent apps screen, select **settings \> watch faces and styles \> watch faces**. 4. swipe right until you find your application icon, and select it. the **clock changed** message is displayed. 5. press the **back** key (in the upper-right corner of the emulator device) multiple times, until the home screen with your new watch face is shown.  while the application is running, the **log** view in the tizen studio shows the log, debug, and exception messages from the methods defined in the log macros. to see the view, in the tizen studio menu, go to **window \> show view \> log**. for more information on using the emulator features, see using emulator control keys, menu, and panel and using extended emulator features. running on a target device to run the application on a target device: connect the wearable target device to your computer: define settings on the device: go to settings > connections, and switch on wi-fi. the device and the computer must be connected to the same wi-fi network. note the ip address the device is using. go to settings > gear info, and switch on the debugging mode. in the terminal, enter the following commands: cd tizen-studio/tools ./sdb connect <ip address of galaxy watch> use the ip address you noted before. instead of the terminal, you can also use the remote device manager for the connection. in the first attempt, the connection fails and the device asks for user confirmation. to allow galaxy watch to read log data, copy files to and from your computer, and install the application manually, click the accept mark. in the device manager, confirm that the device is connected (shown in the device list). generate an author certificate. before you run the application, you must sign your application package with a certificate profile in the tizen studio. run the application: in the device manager, select the device. in project explorer view, right-click the project and select run as > tizen native application. alternatively, you can also select the project in the project explorer view and do one of the following: press the ctrl + f11 key. click the run icon in the toolbar. if you have both a connected device and existing emulator instances, select the device from the combo box in the toolbar before selecting to run the application. confirm that the application launches on the target device. like with the emulator, you can change the watch face in the device settings to see the watch application on the home screen. note : the application is launched using the default debug run configuration. to create and use another configuration: in the project explorer view, right-click the project and select run as > run configurations. in the run configurations window, click the new launch configuration icon (), define the configuration details, and launch the application by clicking run. designing a simple ui the wearable watch application created with the watch template has a simple user interface with a label component showing the hello watch text and the current time (hour, minute, and second). the ui is created using efl. in the ambient mode, the watch template ui is identical to the normal ui, except that is shows the current time without the seconds. figure: user interface in the watch template (ambient mode on the right) creating the basic ui the ui in the watch template contains the following components: the efl ui always contains a window component, which is the root component of the entire ui. the application uses the conformant component as a container for other ui components. the label showing the hello watch text and the current time is implemented with a label component. the ui is created in the watch.c file: data structure a pointer to the ui components is stored in the appdata_s data structure: struct appdata { /* window */ evas_object *win; /* conformant */ evas_object *conform; /* label */ evas_object *label; }; typedef struct appdata appdata_s; ui creation the app_create() life-cycle callback is called when the application main loop starts, and it calls the create_base_gui() function to create the ui: static bool app_create(int width, int height, void *data) { /* define system callbacks */ appdata_s *ad = data; create_base_gui(ad, width, height); return true; } ui components the create_base_gui() function creates the ui components: window, conformant, and label. the function receives a pointer to fill in the appdata_s structure. static void create_base_gui(appdata_s *ad, int width, int height) { the window object of the idle screen is retrieved with the watch_app_get_elm_win() function of the watch application api. the watch_time_h handle is created for managing the current time, and the evas_object_resize() function is used to resize the window to fit the screen. int ret; watch_time_h watch_time = null; ret = watch_app_get_elm_win(&ad->win); if (ret != app_error_none) { dlog_print(dlog_error, log_tag, "failed to get window. err = %d", ret); return; } evas_object_resize(ad->win, width, height); the conformant component is used as a container for the other ui components: the component is the first object added inside the window with the elm_conformant_add() function. the conformant component is set as a resize object of the window by using the elm_win_resize_object_add() function. it means that the conformant size and position are controlled by the window component directly. the evas_object_show() function makes the conformant component visible. ad->conform = elm_conformant_add(ad->win); evas_object_size_hint_weight_set(ad->conform, evas_hint_expand, evas_hint_expand); elm_win_resize_object_add(ad->win, ad->conform); evas_object_show(ad->conform); the label component for the text and time is added with the elm_label_add() function. the label is added inside the conformant component, which is the label's parent. the label is resized and moved so that it is located below the first third of the screen height. ad->label = elm_label_add(ad->conform); evas_object_resize(ad->label, width, height / 3); evas_object_move(ad->label, 0, height / 3); evas_object_show(ad->label); the watch_time_get_current_time() function retrieves the current time, and the update_watch() function uses the current time to set the label component content. finally, the watch_time_h handle is deleted. ret = watch_time_get_current_time(&watch_time); if (ret != app_error_none) dlog_print(dlog_error, log_tag, "failed to get current time. err = %d", ret); update_watch(ad, watch_time, 0); watch_time_delete(watch_time); when all the ui components are ready, the evas_object_show() function makes the window component visible. this means that the window displays everything on the screen at once. evas_object_show(ad->win); } modifying existing components when the basic ui exists, you can easily modify the components in the ui by using the component-specific functions, or more general evas object functions. for example, the following modification to the label component changes the text color to red: ad->label = elm_label_add(ad->conform); evas_object_color_set(ad->label, 255, 0, 0, 255); evas_object_resize(ad->label, width, height / 3); evas_object_move(ad->label, 0, height / 3); evas_object_show(ad->label); figure: modified label component showing the current time you can update the time on the screen with the time_tick (in the normal mode) or ambient_tick (in the ambient mode) callback: both callbacks contain the current time handle, and call the update_watch() function to update the label content on the screen: static void app_time_tick(watch_time_h watch_time, void *data) { appdata_s *ad = data; update_watch(ad, watch_time, 0); } static void app_ambient_tick(watch_time_h watch_time, void *data) { appdata_s *ad = data; update_watch(ad, watch_time, 1); } in the update_watch() function, the watch_time_h handle is used to retrieve the current time elements (hour, minute, and second) with the watch_time_get_hour24(), watch_time_get_minute(), and watch_time_get_second() functions of the watch application api. the text for the label component is defined (based on whether the normal or ambient mode is used), and set with the elm_object_text_set() function. static bool update_watch(appdata_s *ad, watch_time_h watch_time, int ambient) { char watch_text[text_buf_size]; int hour24; int minute; int second; if (watch_time == null) return; watch_time_get_hour24(watch_time, &hour24); watch_time_get_minute(watch_time, &minute); watch_time_get_second(watch_time, &second); if (!ambient) { snprintf(watch_text, text_buf_size, "<align=center>hello watch<br/>%02d:%02d:%02d</align>", hour24, minute, second); } else { snprintf(watch_text, text_buf_size, "<align=center>hello watch<br/>%02d:%02d</align>", hour24, minute); } elm_object_text_set(ad->label, watch_text); }
