Registering Applications

This guide explains how to register and update a TV application.

Creating New Application

To register a new application, click the "Create App" button in the "Applications" list.

Figure 1. Create new application

On the application creation page, enter the application name, application type, and default language to create a new application ID.

At this time, the entered application name and generated application ID are used as application identifiers, so they cannot be duplicated and cannot be changed after creation.

The application name you enter when creating an application is the name used for application management within the TV Seller Office system, regardless of the application title displayed on TV.
Also, the application ID generated by the TV Seller Office is independent of the Tizen ID of the application package.

Input Field Description Mandatory Updatable
Application Name

Enter the application name to be used for management purposes within this system. Yes No
App Type

Choose between a Tizen web application or a .NET application. Yes No
Default Language

Choose the default language for the application. Yes Yes

Table 1. Application information input fields

Enter all the information and click the "Done" button to create the application.

Immediately after creating the application, you can enter the necessary information for the application service and upload the application package.

Uploading Application Package

When registering the first version of an application that has been developed, or when registering an upgraded version with features added or defects resolved, you must first upload the application package file to distribute the application.

If you click the "Upload" button in the "Applications > App Package" list, the application upload page is displayed.

Figure 2. Uploading application package

For Tizen web applications, upload the application files with a .wgt extension, and for Tizen .NET applications, upload them with a .tpk extension. The extension must be lowercase.

When uploading is complete, a pre-test is automatically executed, and the result of checking and detecting the settings and applied functions in the application package is immediately provided on the screen.

The items that the pre-test tool checks include:

Criteria Check Item
.wgt or .tpk

  • Package file format must be supported by platform and the file extension must be lowercase.
  • The file name cannot cotain special characters other than spaces and underscores (_) and cannot exceed 100 bytes.
config.xml

  • For Tizen web applications, the file "config.xml" must be in the package.
  • Required information such as Tizen ID, Application Version, API Version, Application Title, and Screensize must be defined.
  • The Samsung TV SDK for Tizen automatically generates a unique Tizen Application ID for the application package. Two different Tizen applications cannot be registered with the TV Seller Office using the same Tizen ID.
  • When uploading a new package to an existing Tizen application, you must use the same Tizen ID as the previous version.
  • When building a project in Tizen Studio, the Package ID must be unique and cannot contain special characters. If an app is already registered in TV Seller Office with the same package name, you cannot register it.
  • The estimated value of the Tizen package version is [0-255].[0-255].[0-65535]. If you want to register an application with the TV Seller Office with a new application ID, you can use a version number that fits this range. Example: 123.123.12345
  • When you upload a new package, it must not overlap with the version of the existing package.
  • The value of required_version tag must meet the standard x.y format. Example: 2.4
  • Screen size information must be specified in feature tag of configuration file.
  • The Samsung TV SDK for Tizen provides 3 levels of privileges: public level, partner level, platform level. As per Samsung policy, partner-level APIs are only available for Samsung Smart TV partners.
  • The smartcontroller.microphone API should not be declared arbitrarily because only pre-consulted applications are available it.
  • The keymanager, systemmanager, and websetting APIs are no longer available.
  • The auto restart feature is not available. The value of the auto-restart or on-boot tag must not be specified as "true".
  • The background support feature is available only for pre-consulted applications. The value of the background-support tag must not be specified as "enable".
  • If the base_screen_resolution tag is defined, it must be specified with a value of "extensive" or "fullscreen".
  • If the use.continue_watching tag is defined, its value must be specified as "bg_service".
  • The casting.protocol.dial tag should not be declared arbitrarily because only pre-consulted applications are available it.
  • The nodisplay tag is only available to Samsung Smart TV partners.
  • If the linkeddevice.support tag is defined, its value must be specified in the standard YYY::XXX format. (YYY = LINK_DEVICE_TYPE, XXX = LINK_DEVICE_ID)
  • If the multiview_support or multiview_support_new tag is defined, it must be specified with a value of "true" or "false".
  • If the use.drm tag is defined, it must be specified with a value of "true" or "false". The "false" value should not be arbitrarily specified because the uncryption function is only applicable for pre-consulted applications it.
  • If the pointing.device.support or pointing-device-support tag is defined, it must be specified with a value of "enable" or "disable".
  • If the value of the use.preview or use.accelerator tag is "endpoint_URL", the URL must be specified together.
  • If the Provider.ID tag is defined, its value (10 digits) must be specified and the MDE.content.continuity tag must be defined together. The MDE.contents.continuity tag must have its value specified as "effortless.login" or "contents.continuity".
  • If the required-services tag is defined, the values "service name" and "min-version" must be specified with the service tag.
  • If the requires tag is defined, the values "id", "storeid", and "version" must be specified together. This tag should not be used arbitrarily because it is only available to pre-consulted sellers.
  • The ticker feature is not available on the Tizen platform. The ticker tag must not be defined in configuration file.
  • If the tvkey.config tag is defined, its value must be specified. This tag should not be used arbitrarily because only pre-consulted applications are available it.
  • If the use.uwe tag is defined, it must be specified with a value of "true" or "false". UWE should not be arbitrarily specified as "true" because only pre-consulted applications are available it.
  • If the content.zoom.fill tag is defined, it must be specified with a value of "enable" or "disable".
tizen-manifest.xml

  • For Tizen .NET applications, the file "config.xml" must be in the package.
  • Required information such as Tizen ID, Application Version, API Version, Application Title, and Screensize must be defined.
  • The Samsung TV SDK for Tizen automatically generates a unique Tizen Application ID for the application package. Two different Tizen applications cannot be registered with the TV Seller Office using the same Tizen ID.
  • When uploading a new package to an existing Tizen application, you must use the same Tizen ID as the previous version.
  • When building a project in Tizen Studio, the Package ID must be unique and cannot contain special characters. If an app is already registered in TV Seller Office with the same package name, you cannot register it.
  • The estimated value of the Tizen package version is [0-255].[0-255].[0-65535]. If you want to register an application with the TV Seller Office with a new application ID, you can use a version number that fits this range. Example: 123.123.12345
  • When you upload a new package, it must not overlap with the version of the existing package.
  • The value of required_version tag must meet the standard x.y format. Example: 2.4
  • Screen size information must be specified in feature tag of configuration file.
  • The Samsung TV SDK for Tizen provides 3 levels of privileges: public level, partner level, platform level. As per Samsung policy, partner-level APIs are only available for Samsung Smart TV partners.
  • The smartcontroller.microphone API should not be declared arbitrarily because only pre-consulted applications are available it.
  • If the ui-application or service-application or wideget-application tag is defined, the value "type" must be specified together.
  • If the background-update tag is defined, its value must be specified together.
  • If the base_screen_resolution tag is defined, it must be specified with a value of "extensive" or "fullscreen".
  • If the use.continue_watching tag is defined, its value must be specified as "bg_service".
  • The casting.protocol.dial tag should not be declared arbitrarily because only pre-consulted applications are available it.
  • The nodisplay or display.hidden tag is only available to Samsung Smart TV partners.
  • If the multiview_support or multiview_support_new tag is defined, it must be specified with a value of "true" or "false".
  • For Tizen .NET applications, the pre-loading function is only available for pre-consulted applications. The value of the prelaunch.support tag must not be specified as "true".
  • If the value of the use.preview or use.accelerator tag is "endpoint_URL", the URL must be specified together.
  • If the Provider.ID tag is defined, its value (10 digits) must be specified and the MDE.content.continuity tag must be defined together. The MDE.contents.continuity tag must have its value specified as "effortless.login" or "contents.continuity".
  • If the required-services tag is defined, the values "service name" and "min-version" must be specified with the service tag.
  • If the requires tag is defined, the values "id", "storeid", and "version" must be specified together. This tag should not be used arbitrarily because it is only available to pre-consulted sellers.
  • If the mountinstall.sqaushfs tag is defined, it must be specified with a value of "true" or "false".
  • The ticker feature is not available on the Tizen platform. The ticker tag must not be defined in configuration file.
  • If the tv-info tag is defined, the value "api-version" must be specified and the infolink tag must be defined together.
  • If the use.uwe tag is defined, it must be specified with a value of "true" or "false". UWE should not be arbitrarily specified as "true" because only pre-consulted applications are available it.
  • If the content.zoom.fill tag is defined, it must be specified with a value of "enable" or "disable".
author-signature.xml

  • There must be an "author-signature.xml" file in the package.
  • "author-signature.xml" file must be valid.
  • When uploading a new package to an existing Tizen application, the author information must be the same as the existing version.
signature1.xml

  • There must be a "signature1.xml" file in the package.

Table 2. Pre-testing criteria

If the pre-test fails, the application package cannot be registered. In this case, review and fix all issues found and upload the application package again.

Finally, select whether to share the application source file with your group members and click the "Done" button to complete the application package registration.

Application Version Status

Registered application packages are provided in the "'Applications > App Package" list with version information.

Ready to Submit

This is a version that has not yet been released, and can be deleted at any time.

Submitted

This is a version that has been requested to be released, and may be rejected by some model groups depending on the certification and verification result.

Alpha Testing

This version has not been released on the App Store and is undergoing alpha testing.

Versions in the alpha test process cannot be requested to be released, but they can be released after the alpha test ends.

Also, the service country cannot be changed while the alpha test is in progress. Once the test is completed, this restriction is lifted.

Alpha Test Closed

This version has not been released on the App Store and has been alpha tested.
You can request a release of the service for a version that has been alpha tested.

Deleting Applications No Longer Used

You can delete applications that have not yet been distributed or for which the service has been completely terminated, that is, applications with a status of 'Under Registration' or 'Terminated'.

The "Delete" button is shown for applications that can be deleted from the "Applications" list. If you click the button, the application is deleted after a confirmation.

Figure 3. App list

You can also delete unreleased versions of applications that are in the 'Ready to Submit' status.

The "Delete" button is shown for versions that can be deleted from the "Applications > App Package" list. If you click the button, the application is deleted after a confirmation.

Figure 4. App Package list

Deleted applications and deleted versions cannot be recovered.