Wednesday, 26 March 2014

Make a samsung gear

Samsung Gear
Samsung GearSamsung Gear Application is consisted 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, Accessory package, in Samsung Mobile SDK, is the necessary component for communicating between the Host-side Application and Wearable-side Widget. You can find more details below.

Download
For developing Samsung Gear Application, you need both of the Tizen SDK for Wearable and Samsung Mobile SDK(Accessory package). You can find more details on how to develop Gear Application in the ‘Getting Started’ document below.
Category
Download Link
Description
SDK
1.0.0b1
1.5 beta1
Documentation
Provides guidelines on how to develop Gear Applications.
Provides guidelines for Samsung Gear UI design.
Architecture
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
Application Package Structure
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. 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.
Certification Process for Testing Apps on Actual Devices
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.
To sign your code for actual device, you need to create your certificate. You can create CSR(Certificate Signing Request) file and RSA key pair by using Tizen IDE for Wearable with actual device ID which you want to test.
You can request sign to your CSR to certificate authority (CA) by sending CSR file to gear2.sec@samsung.com, then, CA will return signed certificate_registration.xml file. This mailing exchange process requires PGP tool to secure your information.
Last step is registering certificate_registration.xml file to the IDE. It will use RSA key in your host which is created at first step and generate your final certificate which enables you to test in actual devices.
You can find more detailed for the certificates in Help Contents of the IDE(Help Contents > Getting Started with Tizen Wearable > Tizen SDK for Wearable > Certificates).
App Distribution through Samsung Apps
Gear Applications you develop will be distributed through slightly different Samsung Apps. A special Samsung 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 separate Samsung Apps.
Figure 5: Samsung Apps for Gear Apps inside the Gear Manager
Figure 5: Samsung Apps for Gear Apps inside the Gear Manager
App Distribution Process
  • 1) Connect to Samsung Apps Seller Office
  • 2) Set up your account and login
  • 3) Preparing and submitting your app through ‘Add New Application’ menu
  • 4) App distribution will be completed after reviewing your app
Figure 6: Selecting Gear App Type in Samsung Apps Seller Office

Figure 6: Selecting Gear App Type in Samsung Apps Seller Office

0 comments:

Post a Comment