Overview of Web and Native API Frameworks
The Tizen platform supports two primary application types.
- Web apps are Internet-enabled apps that are accessible via the mobile device’s Web browser. A Web framework provides state-of-the-art HTML5/W3C APIs, web UI framework, supplementary APIs, and additional Tizen device APIs. Web is strong in portability, ease of app development, and has a minimal learning curve.
- A Native framework supports full-featured Native application development and provides a variety of features, such as background service and image and face recognition. Native apps use the Native API, which provides all of the memory management and performance benefits that go with building applications for Linux in C.
For more detailed information about Web and Native APIs, see the following links:
|Web and Native Applications||Differences between Tizen Web-specific and Native-specific applications, Tizen architecture, and Tizen documentation.||https://developer.tizen.org/development/getting-started/overview|
|Web App Introduction||Guides you to familiarity with Tizen Web API programming and application models.||https://developer.tizen.org/development/getting-started/web-application|
|Web App Development||Helps you create and develop your first Web app.||http://developer.samsung.com/gear/develop/creating-your-first-app/web|
|Native App Introduction||Guides you to familiarity with Tizen Native API programming and application models.||https://developer.tizen.org/development/getting-started/native-application|
|Native App Development||Helps you create and develop your first Native app.||http://developer.samsung.com/gear/develop/creating-your-first-app/native|
Standalone and Companion Apps
A Gear app that was developed using either Web or Native application can be either a standalone or a companion app.
A standalone Gear app can function on its own and does not require any other app to execute its functionality.
- Standalone Gear apps may or may not need network connectivity (for example, the Calculator app does not need network connectivity in order to function).
- Standalone apps can also handle authentication on the Gear application.
Companion apps consist of two apps working together. One app runs on the Gear device, and the other is an Android app running on the Android device.
- Most companion apps use the phone's connectivity to communicate to the cloud. If the Gear device is no longer connected to the phone, it can use its own WiFi connectivity (or 3G) to talk to the cloud.
- Gear companion apps can take advantage of Android companion apps to get user credentials.
- Samsung provides a Samsung Accessory Protocol (SAP) library (Samsung Accessory SDK), which can be downloaded separately. SAP library has all the APIs necessary to handle the communication between Gear and Android apps.
- To enable host devices such as the phone to recognize companion apps, specific metadata must be declared on both the host Android app's manifest file and on the Gear app’s config.xml or Tizen manifest file. For more information, see http://developer.samsung.com/gear/develop/creating-your-first-app/web-companion/configuration
Tizen SDK Downloads
|Tizen SDK||SDK to develop standalone and companion Gear apps based on the Tizen Web API or Native API.|
|Download||Source for Tizen SDK files, SDK tools, and IDE tools||http://developer.samsung.com/gear/develop/sdk|
|Installation||Tizen SDK overview, prerequisites, installation, updating, extension SDKs, and uninstalling||https://developer.tizen.org/development/tizen-studio/download/installing-tizen-studio|
|Tizen Extension SDK||SDK to install the certificate extension (to generate Gear certificates) and the wearable extension on Gear devices.|
|Installation||Step-by-step procedure to install the extension SDK in Tizen Studio||http://developer.samsung.com/gear/develop/creating-your-first-app/web-companion/setup-sdk|
Samsung Accessory SDK
|SAP enables Gear apps to communicate with Android apps|
|Download||Link to the Samsung Accessory SDK and its resources||http://developer.samsung.com/galaxy/accessory|
|Programming||Link to the Samsung Accessory programming guide||http://developer.samsung.com/galaxy/accessory/guide|
You can design and create interactive widget applications that run on Gear wearable devices and display glanceable information to users. Widgets can include action events in response to screen taps by users.
Widgets are located on the right side of the watch face and are accessed by rotating the Gear’s bezel. Because they’re easy to use while you're on the move, they’re a great opportunity to engage with users. Widgets also act as a shortcut to your Gear application. For more information about widgets, see the following links:
|Web widget development||http://developer.samsung.com/gear/de...app/web-widget|
|Native widget development||http://developer.samsung.com/gear/de...rst-app/native|
|Programming guide for Web widgets||https://developer.tizen.org/developm...et-application|
|Programming guide for Native widgets||https://developer.tizen.org/developm...ion-management|
Gear In-App Items
Within Gear apps (companion or standalone, Web or Native), you can sell commercial in-app items such as virtual items, increasing levels of play, advanced app features by integrating Samsung Gear In-App Purchase (Gear IAP) functionality.
For more information:
- Gear In-App Purchase section: https://resources-sandbox.mindtouch.us/Galaxy_Devices/In-App_Purchase_Items/Develop/Gear_In-App_Purchase
- Gear In-App Purchase Guide for Native API: http://img-developer.samsung.com/onlinedocs/gear/Extension_PG_Native/html/prog_guide/inapp_wn.htm
- Gear In-App Purchase Guide for Web API: http://img-developer.samsung.com/onl...e/inapp_ww.htm