Samsung Gear

Tizen SDK for Wearable 1.0.0

Oct 6, 2014

Samsung Accessory SDK 2.1.11

Oct 6, 2014

For developing Samsung Gear Application, you need both of the Tizen SDK for Wearable and Samsung Accessory SDK. You can find more details on how to develop Gear Application in the 'Hello Accessory Developer's Guide' document below.

Samsung Gear Application consists of the Host-side Application which runs on Android-based Samsung mobile devices, and the Wearable-side Widget which runs on Tizen-based Samsung Gear devices.

The Host-side Application can be developed in the common Android development environment, whereas, the Wearable-side Widget can be developed with Tizen SDK for Wearable.

In addition, Samsung Accessory SDK, is the necessary component for communicating between the Host-side Application and Wearable-side Widget. You can find more details below.

What Can I do with SDKs for Samsung Gear S?

  • Enhanced Standalone Features

    Develop enhanced standalone Gear app with enhanced network, call and Location-based APIs. Samsung Gear S can solely connect 3G network without mobile devices.

  • New Sensor APIs

    Try Magnetic, Ambient Light, Barometer, and UV Sensor APIs which are added newly as well as Accelerometer and Gyroscope APIs.

  • Rich Notification

    Create variety of notifications for Gear using Samsung Rich Notification SDK. Rich Notification SDK

  • Data Transfer

    Connect GALAXY device to Gear device, and send messages, data, and files using Samsung Accessory SDK. Accessory SDK

How Can I Develop a Gear Application?

  1. SDK
    Download

    Tizen SDK for Wearable Samsung Accessory SDK

    >> Download Links

  2. Gear App Development

    Getting Started with samples & Documents!

    >> Technical Resource

  3. Getting
    the Gear
    Certificate

    Be secure your app to upload to Samsung Gear Apps

    >> Certification Guide

  4. Testing

    If you have no Gear device, Use Gear Emulator & RTL

    >> Get Gear Emulator

    >> RTL Service

  5. Registration through Samsung
    GALAXY Apps

    >> Gear App Distribution Guide


    >>Samsung GALAXY Apps Seller Office

Technical Resources

Tutorial Video

Documentation

Samsung Gear SDK Documentation download links
Download Link Description Date
Hello Accessory Developer's Guide Guidelines on how to develop Gear apps. Sep 3, 2014
Programming Guide Guidelines on how to install and uninstall Gear application and configure host application. Oct 6, 2014
How to design apps on Tizen Wearable devices with multi-resolution This document demonstrates how to design your application layout so that your application can run on multiple Tizen devices. Sep 5, 2014
Guideline on Testing Gear
applications using the
Emulator
Guidelines on how to connect host device to Gear Emulator to test SAP and Rich Notification. This will help if you have no Gear device. Sep 3, 2014
UI Design Guidelines for Gear S New Guidelines for Samsung Gear S UI design. Oct 8, 2014
UI Design Guidelines for Gear 2 Guidelines for Samsung Gear 2 UI design. Mar 21, 2014

Samples

Samsung Gear SDK Samples download links
Download Link Description Date
Hello Accessory New Sample application of simple string transfer between a Galaxy device and a Gear. Oct 6, 2014
Gallery New Sample application of byte data(picture) transfer between a Galaxy device and a Gear. Oct 6, 2014
File Transfer New Sample application of file transfer between a Galaxy device and a Gear. Oct 6, 2014
Applications for Emulator Sample, service, core applications to be needed when you test Gear applications using the Emulator via SAP and Rich Notification. Sep 16, 2014
 

Wearable devices are paired with a host device, such as a smartphone or connected tablet, on which they depend for wider connectivity and various services:

  • The Gear Manager manages sending and configuring widgets on the wearable device.
  • The Wearable Manager Service receives and installs widgets on the wearable device, and forwards setting information to the Gear Manager.
  • SAP (Samsung Accessory Protocol) provides a connection between the host and wearable devices and supports various connectivity technologies, such as Wi-Fi, Bluetooth classic, and Bluetooth Low Energy (BLE). For more information, please refer to this web page.

The following figure shows the architecture of the host and wearable device software including the Gear Manager.

Figure 2: Architecture of the host and wearable device

Figure 2: Architecture of the host and wearable device

Applications also consist of 2 parts: host applications and wearable-side widgets. Usually, a wearable-side widget and a corresponding application running on the host device operate as a provider and consumer pair. Host applications are developed using the Android APIs, whereas the wearable-side widgets are developed using a Tizen wearable platform. The following figure shows the relationship between the host SDK and wearable SDK.

Figure 3: Host SDK and wearable SDK

Figure 3: Host SDK and wearable SDK

The Tizen SDK for Wearable allows you to develop the following types of Gear applications:

  • Linked (Master-Follower)
  • Integrated
  • Standalone

Gear applications for Linked (master-Follower) and Integrated type consist of a host-side application package (APK) and a wearable-side widget, while gear applications for Standalone type are only wearable-side widgets. The following figure illustrates the structure of each application type.

Figure 4: Application package structure

Figure 4: Application package structure

Linked (Master-Follower) Type

The linked Gear application is not included with the general host application. You must install the general host application and the wearable-side widget separately.

Integrated Type

In an integrated Gear application, the host-side APK contains the general host application. When you download an integrated Gear application, the general host application in the host-side APK is installed simultaneously with the wearable-side widget.

Standalone Type

You can use the standalone type, such as a Clock app, when your Gear application does not need a general host application, and can operate independently.

Code signing protects your application from modification and ensures your ownership during version upgrade process.

Code signing is used in combination with device information. This ensures your signed application run only on test devices which you specify. It ensures your application cannot be distributed by someone else even though your application package is leaked.

You have to take the certification steps not only for testing your apps on the actual devices but also for uploading your apps to Samsung GALAXY Apps Seller site. If you do not have any actual device but want to upload your apps to Samsung GALAXY Apps Seller site, please get and use the virtual Device Unique ID below. You can find more detailed for the certificates in Help Contents of the IDE(Help Contents > Getting Started with Tizen Wearable > Development Environment > Tizen SDK for Wearable > Certificates).

Get the virtual Device Unique ID

The virtual Device Unique ID copied to clipboard: OYbnFSmxwxVOk62e/cz11DU+J90=

To sign your code for actual device, you need to retrieve an author certificate and a device profile for test devices. First, you create CSR(Certificate Signing Request) file and identify the Device Unique ID which you want to test by using Tizen IDE for Wearable.

Now, you can request your CSR by uploading the created CSR file and a device profile by entering Device Unique IDs to Samsung Developer Center. Then, they will return signed author.crt and device-profile.xml file. Last step is registering author.crt and device-profile.xml file to the IDE. It will generate your final certificate which enables you to test in actual devices.

When you are developing with Tizen Wearable SDKs above 1.0.0.b3, and if you already have author.crt file in keystore directory, please import that file and do not re-create it. Especially, if your application is on sale, do not change the author certificate because it can cause a problem when updating the application. Matching the author certificate guarantees the updating, and of course, re-creating the device-profile does not affect the application updating.

Gear Applications you develop will be distributed through slightly different Samsung GALAXY Apps, Samsung Gear Apps. The Samsung Gear Apps only for Samsung Gear has been constructed inside the Gear manager. Without getting confused with mobile apps, Gear users can easily find and download the Gear apps they want through this Samsung Gear Apps.

Figure 5: Samsung Gear Apps inside the Gear Manager

Figure 5: Samsung Gear Apps inside the Gear Manager

App Distribution Process
  • 1) Connect to Samsung GALAXY Apps Seller Office
  • 2) Set up your account and login
  • 3) Click 'Add New Application' button and then select 'Samsung GALAXY Gear' to submit your Gear app
  • 4) App distribution will be completed after reviewing your app
    Figure 6: Samsung GALAXY Apps Seller Office

    Figure 6: Samsung GALAXY Apps Seller Office

Figure 7: Selecting Gear App Type

Figure 7: Selecting Gear App Type

go to top