ArkTS
General-purpose compiled programming language
- 8 min read
- 6 chapters
Related on Lably
Through High-level programming language, Open source and JavaScript
Huawei intended ArkTS to support many core concepts associated with extended TypeScript (eTS) based on TypeScript and in turn JavaScript from previous versions of HarmonyOS 3.0 with ArkUI declarative UI app development and 2.0 imperative app development alongside Java. ArkTS was introduced at Huawei's Developer Conference (HDC) 2022 in November 2022 on HarmonyOS 3.1 release.
It underwent an upgrade in HDC 2023 with HarmonyOS 4.0 API 10 and a major upgrade at January 18, 2024 HarmonyOS Ecology Developer Conference alongside, new Cangjie programming language announced by Huawei where both programming languages become the primary languages for the iterative HarmonyOS NEXT system version of HarmonyOS operating system.
The current version of ArkTS, was released on October 26, 2023, for open source OpenHarmony 4.0 API 10 with new ArkTS APIs via DevEco Studio 4.0 Canary build after HarmonyOS 4.0 release on August 4, 2023. Following current stable release, a preview released in January 2024, with OpenHarmony 4.1 Beta 1 API 11. Alongside, internal HarmonyOS NEXT Developer Preview 1 and 2 with latest API 11-12 preview based on latest version of OpenHarmony that features advanced syntax that is matured on the 5.0 version of the DevEco Studio integrated development environment (IDE) that is syntactically rigorous and provides more complete and rich capabilities compared to previous versions.
History
Development of ArkTS started in 2015 by HarmonyOS founder Wang Chenglu, with the eventual collaboration of many other programmers at Huawei at that time began development of HarmonyOS after being incubated in the R&D labs for a few years as earlier as 2012 within the company. ArkTS was motivated by the need for a replacement for Huawei's earlier programming language Java that not only carried legal baggage but also performance issues, underdeveloped applications in a weaker SDK both HarmonyOS 1.0 Vision TV, IoT and HarmonyOS 2.0 expanded version shipped with and improvements that still lacked in HarmonyOS 3.0 eTS/JS development for HarmonyOS app development that lacked modern features for the modern operating system. ArkTS took language ideas from the likes of TypeScript, Swift, Rust, JavaScript. In November 2022, Huawei revealed the programming language evolved from eTS on HarmonyOS 3.0 to ArkTS on HarmonyOS 3.1 update. A beta version of the programming language was released to registered Huawei developers at the conference and it was not open-sourced at that time until OpenHarmony 3.0 API 7 era under OpenAtom Foundation when Huawei contributed the ArkTS codes and APIs of HarmonyOS 3.0 which was formerly named eTS in September 2021.
During HDC 2021, in October 2021, Huawei announced ArkUI with DevEco Studio 3.0 for HarmonyOS 3.0 era, which provides a framework for declarative user interface (UI) structure design across all Huawei devices for eTS development which evolved into ArkTS development by HDC 2022 for HarmonyOS 3.1. ArkTS first appeared on OpenAtom's OpenHarmony 3.1 Beta on December 31, 2021 alongside its documentation. Since December 2023, ArkUI is evolved into OpenHarmony 4.0, also Eclipse Foundation global OpenHarmony-based Oniro with ArkTS programming language support and APIs. Also, Huawei announced it would evolve ArkUI into a cross-platform declarative UI named ArkUI-X to reduce app development time and costs by porting it to multiple platforms on Android, iOS, Microsoft Windows and macOS, etc. Including EulerOS in containers that shares HarmonyOS application software stack technologies making it easier for interoperability.
Version history
Version history of ArkTS releases with OpenHarmony (API 7) and HarmonyOS (API 8) convergence SDK.
Platforms
ArkTS supports the operating systems HarmonyOS, Linux, Windows, macOS, iOS, and Android.
ArkTS is designed to interoperate existing eTS and JavaScript codes previously developed for Huawei products above HarmonyOS, such as HarmonyOS Design language system, graphical user interface (GUI) system. On Huawei devices running HarmonyOS, it links with the eTS runtime library, which allows native application programming interfaces (APIs) in DevEco Studio templates, C, C++, and ArkTS code to run within one program.
Sign in to keep reading
5 more chapters are free with a Lably account.
Features
ArkTS is a general purpose programming language that employs modern programming-language theory concepts and strives to present a simple, yet powerful syntax. ArkTS incorporates innovations and conventions from various programming languages, with notable inspiration from TypeScript, which it replaced as the primary development language on HarmonyOS.
ArkTS was designed to be easy, safe while not sacrificing speed. By default ArkTS manages all memory automatically and ensures variables are always initialized before use. Array accesses are checked for out-of-bounds errors and integer operations are checked for overflow. Protocols define interfaces that types may adopt, while extensions allow developers to add functionality to existing types. ArkTS enables object-oriented programming with the support for classes, subtyping, and method overriding. Optionals allow nil values to be handled explicitly. Concurrent programs can be written using async/await syntax and actors isolate shared mutable state in order to eliminate data races.
Examples
The following is an example of a simple Hello World program. It is standard practice in ArkUI with ArkTS programming language to separate the application struct and views into different structs, with the main view named Index.
<span id="mw_g"></span><span class="k" id="mw_w">import</span><span class="w" id="mwAQA"> </span><span class="nx" id="mwAQE">ArkTS</span> <span class="c1" id="mwAQI">// Index.ets</span> <span class="k" id="mwAQM">import</span><span class="w" id="mwAQQ"> </span><span class="nx" id="mwAQU">router</span><span class="w" id="mwAQY"> </span><span class="kr" id="mwAQc">from</span><span class="w" id="mwAQg"> </span><span class="s1" id="mwAQk">'@ohos.router'</span><span class="p" id="mwAQo">;</span> <span class="kd" id="mwAQs">@Entry</span> <span class="kd" id="mwAQw">@Component</span> <span class="nx" id="mwAQ0">struct</span><span class="w" id="mwAQ4"> </span><span class="nx" id="mwAQ8">Index</span><span class="w" id="mwARA"> </span><span class="p" id="mwARE">{</span> <span class="w" id="mwARI"> </span><span class="kd" id="mwARM">@State</span><span class="w" id="mwARQ"> </span><span class="nx" id="mwARU">message</span><span class="o" id="mwARY">:</span><span class="w" id="mwARc"> </span><span class="kt" id="mwARg">string</span><span class="w" id="mwARk"> </span><span class="o" id="mwARo">=</span><span class="w" id="mwARs"> </span><span class="s1" id="mwARw">'Hello World'</span> <span class="w" id="mwAR0"> </span><span class="nx" id="mwAR4">build</span><span class="p" id="mwAR8">()</span><span class="w" id="mwASA"> </span><span class="p" id="mwASE">{</span> <span class="w" id="mwASI"> </span><span class="nx" id="mwASM">Row</span><span class="p" id="mwASQ">()</span><span class="w" id="mwASU"> </span><span class="p" id="mwASY">{</span> <span class="w" id="mwASc"> </span><span class="nx" id="mwASg">Column</span><span class="p" id="mwASk">()</span><span class="w" id="mwASo"> </span><span class="p" id="mwASs">{</span> <span class="w" id="mwASw"> </span><span class="nx" id="mwAS0">Text</span><span class="p" id="mwAS4">(</span><span class="k" id="mwAS8">this</span><span class="p" id="mwATA">.</span><span class="nx" id="mwATE">message</span><span class="p" id="mwATI">)</span> <span class="w" id="mwATM"> </span><span class="p" id="mwATQ">.</span><span class="nx" id="mwATU">fontSize</span><span class="p" id="mwATY">(</span><span class="mf" id="mwATc">50</span><span class="p" id="mwATg">)</span> <span class="w" id="mwATk"> </span><span class="p" id="mwATo">.</span><span class="nx" id="mwATs">fontWeight</span><span class="p" id="mwATw">(</span><span class="nx" id="mwAT0">FontWeight</span><span class="p" id="mwAT4">.</span><span class="nx" id="mwAT8">Bold</span><span class="p" id="mwAUA">)</span> <span class="w" id="mwAUE"> </span><span class="c1" id="mwAUI">// Add a button to respond to user clicks.</span> <span class="w" id="mwAUM"> </span><span class="nx" id="mwAUQ">Button</span><span class="p" id="mwAUU">()</span><span class="w" id="mwAUY"> </span><span class="p" id="mwAUc">{</span> <span class="w" id="mwAUg"> </span><span class="nx" id="mwAUk">Text</span><span class="p" id="mwAUo">(</span><span class="s1" id="mwAUs">'Next'</span><span class="p" id="mwAUw">)</span> <span class="w" id="mwAU0"> </span><span class="p" id="mwAU4">.</span><span class="nx" id="mwAU8">fontSize</span><span class="p" id="mwAVA">(</span><span class="mf" id="mwAVE">30</span><span class="p" id="mwAVI">)</span> <span class="w" id="mwAVM"> </span><span class="p" id="mwAVQ">.</span><span class="nx" id="mwAVU">fontWeight</span><span class="p" id="mwAVY">(</span><span class="nx" id="mwAVc">FontWeight</span><span class="p" id="mwAVg">.</span><span class="nx" id="mwAVk">Bold</span><span class="p" id="mwAVo">)</span> <span class="w" id="mwAVs"> </span><span class="p" id="mwAVw">}</span> <span class="w" id="mwAV0"> </span><span class="p" id="mwAV4">.</span><span class="kr" id="mwAV8">type</span><span class="p" id="mwAWA">(</span><span class="nx" id="mwAWE">ButtonType</span><span class="p" id="mwAWI">.</span><span class="nx" id="mwAWM">Capsule</span><span class="p" id="mwAWQ">)</span> <span class="w" id="mwAWU"> </span><span class="p" id="mwAWY">.</span><span class="nx" id="mwAWc">margin</span><span class="p" id="mwAWg">({</span> <span class="w" id="mwAWk"> </span><span class="nx" id="mwAWo">top</span><span class="o" id="mwAWs">:</span><span class="w" id="mwAWw"> </span><span class="kt" id="mwAW0">20</span> <span class="w" id="mwAW4"> </span><span class="p" id="mwAW8">})</span> <span class="w" id="mwAXA"> </span><span class="p" id="mwAXE">.</span><span class="nx" id="mwAXI">backgroundColor</span><span class="p" id="mwAXM">(</span><span class="s1" id="mwAXQ">'#0D9FFB'</span><span class="p" id="mwAXU">)</span> <span class="w" id="mwAXY"> </span><span class="p" id="mwAXc">.</span><span class="nx" id="mwAXg">width</span><span class="p" id="mwAXk">(</span><span class="s1" id="mwAXo">'40%'</span><span class="p" id="mwAXs">)</span> <span class="w" id="mwAXw"> </span><span class="p" id="mwAX0">.</span><span class="nx" id="mwAX4">height</span><span class="p" id="mwAX8">(</span><span class="s1" id="mwAYA">'5%'</span><span class="p" id="mwAYE">)</span> <span class="w" id="mwAYI"> </span><span class="c1" id="mwAYM">// Bind the onClick event to the Next button so that clicking the button redirects the user to the second page.</span> <span class="w" id="mwAYQ"> </span><span class="p" id="mwAYU">.</span><span class="nx" id="mwAYY">onClick</span><span class="p" id="mwAYc">(()</span><span class="w" id="mwAYg"> </span><span class="p" id="mwAYk">=></span><span class="w" id="mwAYo"> </span><span class="p" id="mwAYs">{</span> <span class="w" id="mwAYw"> </span><span class="nx" id="mwAY0">router</span><span class="p" id="mwAY4">.</span><span class="nx" id="mwAY8">pushUrl</span><span class="p" id="mwAZA">({</span><span class="w" id="mwAZE"> </span><span class="nx" id="mwAZI">url</span><span class="o" id="mwAZM">:</span><span class="w" id="mwAZQ"> </span><span class="s1" id="mwAZU">'pages/Second'</span><span class="w" id="mwAZY"> </span><span class="p" id="mwAZc">})</span> <span class="w" id="mwAZg"> </span><span class="p" id="mwAZk">})</span> <span class="w" id="mwAZo"> </span><span class="p" id="mwAZs">}</span> <span class="w" id="mwAZw"> </span><span class="p" id="mwAZ0">.</span><span class="nx" id="mwAZ4">width</span><span class="p" id="mwAZ8">(</span><span class="s1" id="mwAaA">'100%'</span><span class="p" id="mwAaE">)</span> <span class="w" id="mwAaI"> </span><span class="p" id="mwAaM">}</span> <span class="w" id="mwAaQ"> </span><span class="p" id="mwAaU">.</span><span class="nx" id="mwAaY">height</span><span class="p" id="mwAac">(</span><span class="s1" id="mwAag">'100%'</span><span class="p" id="mwAak">)</span> <span class="w" id="mwAao"> </span><span class="p" id="mwAas">}</span> <span class="p" id="mwAaw">}</span>ArkUI-X
ArkUI-X is an open-source user interface (UI) software development kit which is extension of ArkUI for ArkTS development created by Huawei. It is used to develop cross platform applications from one codebase for any platform such as Android, iOS, OpenHarmony, Oniro and HarmonyOS which was released on December 8, 2023, after Canary 1 build on August 4, 2023. ArkUI replaces the older Interface Builder paradigm with a new declarative development paradigm.
Ark TypeScript Runtime
ARK TypeScript Runtime is a runtime system used in ArkTS applications derived from former HarmonyOS 3.0/OpenHarmony 3.1 API 8 eTS (extendedTypeScript) on OpenHarmony, and HarmonyOS apps exploiting custom OpenHarmony-based HarmonyOS NEXT core operating system. It contains an allocator and garbage collector (GC) for ArkTS/JS objects, a standard library that conforms to the ECMAScript specification, an interpreter for running the ARK Bytecode (abc) generated by ARK front-end components, an inline cache for acceleration, a statically typed compiler, a C++/C function interface for Native API (NAPI) application development at runtime, and other modules in ahead-of-time compilation via DevEco Studio since version 3.1.1 on both HarmonyOS 3.1 SDK and OpenHarmony 3.2 SDK API 9.
ets_frontend
The ets_frontend is a front-end tool in the ARK Runtime Subsystem which combines the ace-ets2bundle component that supports converting ETS programming language files into ARK bytecode files. They correspond with ArkTS app development in OpenHarmony and HarmonyOS development under HarmonyOS NEXT system.
ArkCompiler Toolchain for debugging
The ArkCompiler Toolchain provides developers with debugging tools for ArkTS application development, such as the Debugger, CPUProfiler, and HeapProfiler. The debugging and tuning capabilities provided by the Ark Toolchain is used through DevEco Studio IDE that relies on the ArkCompiler Runtime to provide runtime-related information to developers.
Development tools
Compiler
With Ark Compiler, it supports a variety of dynamic and static programming languages such as JavaScript, TypeScript, and ArkTS. It is the compiling and runtime base that enables OpenHarmony alongside HarmonyOS NEXT to run on multiple device forms such as smart devices, mobile phones, PCs, tablets, TVs, automobiles, and wearables. ArkCompiler consists of two parts, compiler toolchain and runtime.
IDE and editor support
DevEco Studio for HarmonyOS development using default declarative ArkUI, also other third-party UI frameworks on OpenHarmony SDK, ArkUI-X cross-platform development with Android and iOS support.