Tizen Compliance Program

Why Compliance?

The Tizen Compliance Program ensures devices and applications work correctly together, by setting out requirements for common behavior and providing a validation mechanism to show that the requirements are followed. The Tizen Compliance Program is valuable to the following audiences:

  • Application developers: know how to create compatible applications that work across multiple devices, and how Tizen devices will behave.
  • Tizen device implementers: know how to implement a Tizen compliant device by satisfying software and hardware requirements.
  • Carriers: know how to customize and enhance a device, while remaining within compliance guidelines.
  • End users: know that applications will work on their device and are assured of a consistent user experience among compliant devices and applications.

To become Tizen compliant, a device must obtain Tizen Compliance certification.


The Tizen Compliance Program consists of the following:

  • Tizen Compliance Specification (TCS). The document containing the definitive set of requirements for Tizen compliant devices.
  • Tizen Compliance Tests (TCT)The suite of tests that verify each of the requirements in the TCS.
  • Tizen Compliance certification. The formal review and acceptance of a device that has passed all of the tests and is fully Tizen compliant.

Tizen Compliance Model

To be called Tizen compliant, a Tizen device implementer must obtain Tizen Compliance certification for the device for at least one Tizen Profile. This involves satisfying the requirements of the Tizen Compliance Specification, passing all of the Tizen Compliance Tests, then applying to the Tizen Association for certification.

A Tizen Profile describes the requirements for a category of Tizen devices that have a common application execution environment. Applications are created for a specific target profile and can run on devices compliant to that profile.

Each Tizen Profile is based on Tizen Common Libraries, which are the set of libraries common across all Tizen platforms. The set of libraries helps to unify multiple categories of devices by sharing common platform components.

The current available profile is:

  • Mobile: for handsets, tablets, etc.

Additional profiles are expected in the near future, possibly including:

  • IVI: In-Vehicle Infotainment systems
  • TV: DTV/STB/IPTV systems
  • PC: laptops, convertibles, etc.

The Tizen Compliance Tests measure conformance to the Profile requirements.

Compliance Program Steps

  1. A Tizen device implementer gets the Tizen source code and creates a new Tizen device.

  2. A Tizen device implementer obtains the compliance specification (TCS), compliance tests (TCT), and Tizen branding request form from source.tizen.org. The Tizen device implementer must run the tests on their new Tizen device prior to submitting a Tizen branding request.

  3. Once the new Tizen device passes 100% of the compliance tests, the Tizen device implementer submits the test results with a Tizen branding request form to the Tizen Association.

  4. The Tizen Association reviews, approves, and certifies the device as Tizen compliant. Any technical review required to decide approval or failure will be referred to the Tizen Steering Group by the Tizen Association.


The Tizen Project welcomes feedback and input on Tizen Compliance. If a Tizen device implementer has questions or concerns about the specification or compliance tests they are welcome to discuss these on the Tizen compliance mailing list.

Compliance Specification