AWTK leaves one objective unchecked, ships its stable build as a Baidu netdisk link, and carries two build systems at the root
AWTK = Toolkit AnyWhere(a cross-platform embedded GUI)
At a glance
- What is it?
- zlgopen/awtk is ZLG's Apache-2.0 embedded GUI engine written in C, pushed to master on 2026-10-03 with no tagged releases at all. The useful detail is in the file and the tree: the distribution channel is a netdisk link with an access code, the objectives list has a single unmarked item, and the root carries CMake and SConstruct plus four JSON project files.
- Who is it for?
- AWTK is worth evaluating if you are shipping a UI on an MCU with a DMA2D or PXP block and want one widget vocabulary across desktop and embedded, and it is a poor fit if you need a stable, versioned artifact from a registry, because the repository has no releases and the documented stable build is a netdisk link with an access code.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- zlgopen/awtk3,328 ★ · +4
| Repository | 2026-09-25 | 2026-11-15 |
|---|---|---|
| zlgopen/awtk | 3.3k | 3.3k |
4 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The documented stable build is a netdisk link with an access code
There are three distribution lines in the README and none of them is a release. The repository has no GitHub releases at all, and no version tag is visible.
The first line is the main source repository on GitHub. The second is a mirror on Gitee, which matters for anyone behind a network where GitHub is slow or blocked. The third is labelled stable version pack and points at a Baidu Pan address with an access code of 1cmi.
So the answer to which build is stable is a link to a personal netdisk account, with a code you have to read out of a README to paste into a browser. There is no checksum, no tag, and no statement of what version that archive holds. For a project whose pitch includes stability, distributed across Cortex M3 through desktop, that is the single most consequential line in the file.
It also means the usual reproducibility question has no answer here. A build from master and the archive on the netdisk are not verifiably the same code, and nothing in the repository lets you check.
Eight objectives carry a checkmark and the ninth does not
The Ultimate Objectives section is a list of ten targets with completion marks attached. Embedded applications are checked. Linux, macOS and Windows are checked. Web, Android, iOS and HarmonyOS are all checked, each with its own sibling repository linked.
The tenth line has no mark: support development of 2D mini games.
The Cross-platform section repeats the same gap from the other side, saying that in the future AWTK can also run as mini programs. So the one platform class listed as unachieved is the one the objectives section leaves open, and the two sections agree on it.
Everything else in that list is a repository link rather than a claim, which is the useful distinction. awtk-web, awtk-android, awtk-ios and awtk-harmonyos-next are separate codebases with their own URLs, so those four rows are checkable. The mini games row has no link, no mark and no follow-up note.
The list also frames what AWTK is not aiming at. It is a GUI engine with a small systems toolchain underneath, built by an embedded vendor, and the platform spread is the argument for it rather than an accident.
The repository is bilingual, and the English file is the one you get by default
The first line after the title is a note pointing Chinese-language readers at a second file, README_zh.md, which sits in the root beside the English README.md. Both are first-class entries in the tree, not a translated copy in a locale directory.
That has a practical consequence for anyone reading the documentation, because the two files are not stated to be in sync. Nothing in the English file says which is authoritative or when the other was last touched. For a project whose development is described as happening at ZLG in China, the English file is the one to treat as a summary rather than as the specification.
The developer entry point is a document in the tree, docs/awtk_ecology.md, linked as a joint ecology building plan, and the invitation to contribute sits on a blockquote directly under the introduction. There is also a CONTRIBUTING.md at the root, which the README never mentions.
The screenshots section of the file is image-only, so the demo evidence lives in pictures rather than in anything a reader can parse.
Two build systems and four JSON project files sit in the root
The tree carries both a CMake and an SCons build. There is a CMakeLists.txt, a directory of cmake modules, SDL2Config.cmake, awtk-cmake.md and awtk-config.cmake, plus build_with_cmake.sh. There is a SConstruct at the top level for the SCons path. Alongside them sit awtk_config.py and awtk_config_common.py, a Python configuration layer that either build can consume.
Then there are the JSON files: build.json, build_ui_old.json, project.json and component.json. The second of those is named for an older scheme, which means the root carries the previous generation of build description next to the current one and expects you to know which applies.
The rest of the root is the tooling that the feature claims depend on. .clang-format and format.sh govern style. staticcheck/ and valgrind/ are present as directories. run_ui_test.sh and run_fscript_test.sh are the two test entry points, matching the claim that scripts can be generated for several languages. release_version.sh is the version step, given there are no releases. sync_tkc.sh and 3rd/ are how code from elsewhere enters the tree.
For a newcomer, the build system choice is the first real decision, and nothing in the README picks one for you.
Nine binding targets come from one IDL, including three JavaScript engines
AWTK is written in C. Everything above it is generated: the README says scripts in different languages can be generated by the IDL, and the point of that generation is not a thin mapping. It says the generated code follows the native code styles of the target language, not just the C API exposed as-is.
The list of targets is nine: C, Go, C++, lua, java, python, and JavaScript on three separate runtimes, jerryscript, nodejs and quickjs.
Three JavaScript targets is the unusual part, and they are not interchangeable. A script that has to run inside a microcontroller is a different deployment from one that runs in a build tool on a workstation, and the three runtimes cover both ends. For an embedded product that also has JavaScript tooling around it, that is the feature that decides whether one codebase serves both.
Underneath the bindings sits the other half of the cross-platform claim: a cross-platform library of basic tools covering lists, arrays, strings in both UTF8 and widechar, event emitters, values, objects, file system, mutex, threads, formulas and string analysis. The stated reason is that applications built with AWTK can really run across platforms, which puts the portability burden on that layer rather than on the widget code.
The MVVM layer lives in its own repository and needs no AWTK API
Item nine in the feature list is a model-view-viewmodel framework for embedded software, described as thoroughly separating user interface from business logic. The claims for it are performance, low memory use, more thorough isolation, portability to another GUI, and less code, around 5,000 lines.
The line that matters is the sixth: no need for learning the API of AWTK.
That is a different proposition from the rest of the engine. AWTK itself asks you to learn its widgets, its layout description files, its theme files and its widget and window animation model. The MVVM layer says you can keep your logic out of all of that and port it to another GUI later. The implementation is not in this repository; the README links it to zlgopen/awtk-mvvm.
It currently supports C and JavaScript at present, which is narrower than the nine-language binding list. So the decoupling path is available for two of the languages, and the rest of the spread belongs to the UI layer alone.
The separation is the interesting claim to test first if you are evaluating the engine, because it determines whether a rewrite later is a port or a rewrite.
Stability is argued with named tools, and the root has the config for them
The stability section is a list of practices rather than a claim about defects. Static checks run with cppcheck and facebook infer. Memory is checked dynamically with valgrind. There are approximately 20,000 lines of code for unit testing. The engine has been validated in multiple practical projects, and by multiple platforms and compilers. The list ends with code review and manual test.
Several of those have visible counterparts in the tree, which is more than most feature lists offer. staticcheck/ and valgrind/ are directories at the root. .clang-format plus format.sh is the style gate. run_ui_test.sh and run_fscript_test.sh are the two runners. The thoroughness claim about automation matches a separate line about supporting event recording and playback for stress testing, plus Appium for fully automated UI testing.
The efficiency claims are more concrete. Changed parts are updated with dirty rectangle algorithms. There is optional triple framebuffer support. UI description files and theme files are stored in binary formats so they parse faster. Acceleration covers OpenGL, DirectX, Vulkan and Metal, plus 2D paths for embedded parts, naming NXP PXP and STM32 DMA2D, with other interfaces expected to be adaptable.
No performance figure appears anywhere in the file, which is the honest shape of the claim: mechanism named, measurement absent.
Editorial conclusion
AWTK is worth evaluating if you are shipping a UI on an MCU with a DMA2D or PXP block and want one widget vocabulary across desktop and embedded, and it is a poor fit if you need a stable, versioned artifact from a registry, because the repository has no releases and the documented stable build is a netdisk link with an access code. Before committing, confirm two things: that the platform you target is on the compatibility list rather than the goals list, and that the toolchain you already use is one of the two build systems at the root, since the rest of the configuration assumes one of them.
Frequently asked questions
What is AWTK and who develops it?
AWTK stands for Toolkit AnyWhere and is an open source cross-platform GUI engine for embedded systems developed by ZLG, under the Apache License 2.0. It is also the built-in GUI of AWorksOS, the ZLG IoT operating system.
How do I get a stable release of AWTK?
The repository has no GitHub releases. The README lists a main GitHub repository, a Gitee mirror, and a stable version pack hosted on Baidu Pan with the access code 1cmi.
Which platforms does AWTK already support?
The objectives list marks embedded, Linux, macOS, Windows, Web, Android, iOS and HarmonyOS as done, with separate repositories for the last four. Only 2D mini games is left unmarked.
How do I build AWTK from source?
The root carries two build systems, CMake via CMakeLists.txt and build_with_cmake.sh, and a SConstruct for SCons, along with awtk_config.py and several JSON build descriptions. The README does not choose between them.
Which programming languages can AWTK target?
Binding code is generated by an IDL for C, Go, C++, lua, java and python, plus JavaScript on three runtimes: jerryscript, nodejs and quickjs. The MVVM layer referenced separately supports C and JavaScript.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zlgopen-awtk)Star history chart for your README
[](https://hysenlabs.com/projects/zlgopen-awtk)Was this useful?