As many of you know from checking out the beta release of the 2.3 SDK, the primary native API in Tizen will be changing from OSP to EFL. This generated a lot of questions and a lot of speculation.
I’ve been in touch with one of the teams who was involved in this, and (with their permission) wanted to share some context from them. The main takeaway from below is that OSP is not necessarily going away immediately (a compatibility runtime is in the works for 2.3, at least), but the clear direction for the future of the native API in Tizen is EFL.
—
Tizen Platform is fundamentally developed to support various device profiles, and changes in Native Framework of Tizen 2.3 SDK/Platform were required in order to support low to high-end devices with Tizen Multi-Profiles (Mobile, Wearable).
With this change in Native Framework, the performance of Tizen Platform has been significantly improved:
1) It uses less memory compared to existing Native environment, and performance has been improved due to the decrease in Security Check Overhead.
2) Performance improved due to the direct use of Retained Mode supporting EFL
We are aware that many developers are expressing concerns regarding the changes of Tizen Native Framework, and we are sorry for any technical difficulties OSP application developers might have.
Although Tizen Platform will no longer be supporting OSP, for Samsung Mobile Devices, we are planning to provide Runtime environment to support existing applications developed based on 2.2.1 OSP for the time being. However, in longer term, we ask you to work on converting your OSP applications to run on new Native Framework.
From our next release, we will do our best to support application’s compatibility with Tizen 2.3 Platform. In addition, we promise to make constant updates to Porting Guide and any guide documents required for development.
Update on the primary native API for Tizen 2.3
Hi Everyone,
As many of you know from checking out the beta release of the 2.3 SDK, the primary native API in Tizen will be changing from OSP to EFL. This generated a lot of questions and a lot of speculation.
I’ve been in touch with one of the teams who was involved in this, and (with their permission) wanted to share some context from them. The main takeaway from below is that OSP is not necessarily going away immediately (a compatibility runtime is in the works for 2.3, at least), but the clear direction for the future of the native API in Tizen is EFL.
—
Tizen Platform is fundamentally developed to support various device profiles, and changes in Native Framework of Tizen 2.3 SDK/Platform were required in order to support low to high-end devices with Tizen Multi-Profiles (Mobile, Wearable).
With this change in Native Framework, the performance of Tizen Platform has been significantly improved:
1) It uses less memory compared to existing Native environment, and performance has been improved due to the decrease in Security Check Overhead.
2) Performance improved due to the direct use of Retained Mode supporting EFL
We are aware that many developers are expressing concerns regarding the changes of Tizen Native Framework, and we are sorry for any technical difficulties OSP application developers might have.
Although Tizen Platform will no longer be supporting OSP, for Samsung Mobile Devices, we are planning to provide Runtime environment to support existing applications developed based on 2.2.1 OSP for the time being. However, in longer term, we ask you to work on converting your OSP applications to run on new Native Framework.
From our next release, we will do our best to support application’s compatibility with Tizen 2.3 Platform. In addition, we promise to make constant updates to Porting Guide and any guide documents required for development.
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio