Tizen provides the tools required to manage your native application life-cycle from product conception, through development and release, to end-of-life application retirement.
Figure: Native application development process
The first step in creating a Tizen native application is planning and designing the application using the design tools of your choice.
Once you have finished the application plan and design, you are ready to create the application project.
Tizen Studio provides various project templates that make it easier for you to start coding your application. When you create a new project, you can select a specific template or sample. Based on the selection, The Tizen Native Project Wizard automatically creates basic functionalities that the application has to implement to be able to run. The default project files and folders are also created.
After creating the application project, you can configure the project properties and create the application manifest to achieve the required functionality and features for your application.
Implementing your application consists of:
Designing and creating the application UI (User Interface)
UI Builder is included in Tizen Studio, and functions as a WYSIWYG (What You See Is What You Get) design environment for creating UIs for native applications.
You can also design the application UI using the controls defined in the User Interface guides.
If needed, update the privileges of the application.
Once you have finished implementing your application, you are ready to build your application.
The build configuration is the set of properties which are used in the build process. The build configuration includes the following properties:
You can run your application in the emulator. The device emulator, provided with Tizen Studio, imitates the target environment running Tizen native applications. Using this replicated environment, you can test your application before deploying it to the real target device.
You can also debug your application with the
emulator. The emulator represents the almost identical functionality of the corresponding device model.
The emulator provides the following debugging capabilities:
You can also optimize your application to achieve the best possible performance.
To debug your application with the emulator or the target device, you must first build the application.
You can package your application using Tizen Studio. If you want to register your application in Tizen store, register the author certificate before packaging your application.
If you have made changes to the application after testing it, rebuild the application.
Select the project in the Project Explorer view.
In the project context menu, select Project > Build Signed Package.
After the packaging process is complete, check the package in the project folder to ensure that the packaging was successful.
Tizen supports multi-project applications that combine different types of application templates.
You can develop a UI project with service or widget projects as a package.
To develop a multi-project native application:
Create a service or widget application.
Package a multi-project application using Tizen Studio:
In Tizen Studio, make sure all the applications you want to include in the package are located in the Project Explorer view.
To make the projects appear in the Project Explorer view, you can create new applications, or import existing projects or sample applications into Tizen Studio.
To establish a project reference between a UI application and a service or widget application:
After packaging the multi-project application, the package consists of the application binary, resource, and data files of the root and referenced applications. Their
tizen-manifest.xml files are merged into one. The application ID in the
tizen-manifest.xml must be assigned with the package ID as a prefix.
The service or widget application is built and run automatically
while the UI application is built and run.
Tizen has limited a multi-project application combination policy for device usability. If you do not follow the policy, the submission of your application to Tizen Store can be rejected.
For your convenience, some policies can be allowed in Tizen Studio only. For example, you can make a STANDALONE service application or STANDALONE widget application in Tizen Studio, but these applications can be rejected in Tizen Store.
The following table shows the possible combinations for a native multi-project. 1 means that only one application can be packaged as a sub application, while M means that multiple applications can be packaged as sub applications. The STANDALONE column defines whether the application can be packaged alone as the main application.
|Main project||Sub project||Sub project||Sub project||Sub project||Sub project||Sub project|
The following examples illustrate how to read the above table:
After you have packaged your application, you are ready to certify and publish your application.
To certify and publish your application:
Upload your mobile native application to Tizen Store or your wearable native application to the Samsung Galaxy Apps Store for registration.
After the application is uploaded, the application is signed as a certified application installer package and the
<Application_name>.tpk archive format, which contains the distributor signature, is added by Tizen Store or Samsung Galaxy Apps Store.
Check your application to Tizen Store or Samsung Galaxy Apps Store for validation and selling.
Tizen Store or Samsung Galaxy Apps Store checks whether your application functions properly.
For detailed instructions on how to register your application and submit it for validation and publication in Tizen Store, see Tizen Store Overview and other subtopics within the Distribution section of the Tizen Developers site.
You can also upgrade your application after certification. If you want to withdraw your application from distribution and operation, you need to request for application retirement from Tizen Store or Samsung Galaxy Apps Store.