zlgopen/awtk

AWTK = Toolkit AnyWhere(a cross-platform embedded GUI)

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 20th, 2026
Created on February 21st, 2018
Open Issues & Pull Requests: 425 (+0)
GitHub issues: Enabled
Number of forks: 789
Total Stargazers: 3,324 (+0)
Total Subscribers: 171 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.8 hours
Mean response time: 52.0 days
90th percentile: 29.0 days
Tracked items: 87

How this project is maintained

98% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 63% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 55
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 494 days
Stale 30+ days: 54
Stale 90+ days: 52

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 2

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

AWTK is a cross-platform embedded GUI toolkit designed to run on resource-constrained devices and real-time operating systems.

The toolkit addresses the challenge of building graphical user interfaces for embedded systems where traditional desktop GUI frameworks are too heavy. AWTK provides a lightweight C implementation that can target multiple embedded platforms and RTOSes simultaneously. It abstracts away platform-specific details through a unified API, allowing developers to write GUI code once and deploy it across different hardware and operating system combinations including STM32 microcontrollers, various real-time operating systems, and other embedded environments.

Developers should consider AWTK when building embedded applications that require a graphical interface but operate under strict memory and processing constraints. The toolkit is suited for projects targeting multiple embedded platforms where code reuse across different hardware is valuable. It works well for teams that want to avoid rewriting UI logic for each target platform and prefer a single codebase approach. The project is particularly relevant for applications running on real-time operating systems where deterministic behavior matters.

The project shows consistent development activity with regular commits addressing bug fixes, feature additions, and platform support improvements. The codebase maintains active engagement with issues and pull requests, indicating ongoing maintenance and responsiveness to user needs. Development spans multiple areas including core GUI functionality, platform-specific backends, and integration with various embedded operating systems. The project demonstrates sustained effort in expanding hardware and RTOS compatibility while refining the core toolkit capabilities.