Stringers
yappologistic/CUI · yappologistic

"Smaller than your avatar": a C component library written almost entirely by Claude, gaining 700+ stars in 5 days

What it is A desktop UI library written in C, with about 190 good-looking ready-made components, running on Windows, Mac, Linux and in the browser. The code was almost entirely written by AI.

Why it took off C has never had a UI library with lots of components that looks finished out of the box. AI removed the cost of hand-writing one. The author first got 40k+ views on a Persian tweet reading "smaller than your avatar," then an early user of Dear ImGui posted it to the HN front page, bringing in about 250 stars overnight.

BHow you could ride this Don't build a "Rust / Go version of CUI"; learn the method instead. Find a spot where hand-writing is expensive and AI generation is cheap (e.g., a nice component library for embedded screens, a version that actually works for touch and Chinese text), publish every component as a clickable web demo, have the README own its weaknesses, and light the fire within your own small circle first.

Grade B: the cost is a few days, it relies on no celebrities or big companies, the method is clear, and nobody has copied it yet. But the stars come from being "the first" and the contrast, and the same approach from Ely-GPUI-Components only got 600 stars. HN's dislike of AI-generated big libraries is rising, and real downloads are only about 108, so the window and retention are a bet. Being talked about in small circles
Data (updated daily) · Repo created 2026-11-05 · 1,153 stars · 7 days +203
GitHub · stars
05001k11-0711-1011-1311-1711-201.2k
Data 2026-11-07 → 2026-11-20 (14 days, 14 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

CUI is a UI component library written in C99: about 190 components, looks like the popular web shadcn, zero dependencies, and a full app compiles to about 250 KB. Of 217 commits, 206 are credited to Claude, and the author says so plainly in the README. It fills a gap nobody has wanted to hand-write, and its "every component is clickable in the browser" demo puts that in front of people. The approach could be repeated in another language or domain, but "big libraries generated by AI in one go" are starting to annoy Hacker News, so the novelty won't last long.

"I know Claude wrote it, but the component demo got me"

On 2026 Nov 9 19:35 (UTC), Hacker News veteran hilti submitted a link titled "CUI – Native UI components for C". He had previously posted "How I got a Dear ImGui app through Mac App Store review" on HN and has built several small Mac tools himself, so he's someone in the desktop C/C++ UI space.

The post quickly hit the front page, ending at 164 points and 86 comments. The first comments were "this looks really beautiful" and "like ShadCN, but in C, really elegant." An hour later the mood shifted: someone pointed out "the first commit was 4 days ago, and it's all Claude-written"; 21:54 someone asked "how does a 5-day-old C project get 611 stars? Hard to believe that many people are using C to build UIs"; and another suggested HN add a rule that a project must be up for some number of days before it can make the front page. hilti replied with one line:

I don't post much, but honestly the component demo got me (I know Claude wrote it). It isn't my project, but I'll definitely try this library.

As of Nov 10, the repo had 738 stars and 40 forks (GitHub, 11-10).

What it is

An "immediate-mode" C UI library: you describe the interface with function calls every frame, and the library handles layout, drawing and interaction. It opens its own windows, supports Windows, macOS and Linux, and the same code can be compiled to WebAssembly and run in the browser. Dropping it into a project takes two files (cui.h / cui.c), or you can pull it in with CMake.

It doesn't win on having few components; it wins on having many. Beyond basics like buttons and forms, there are data tables, charts, a code editor, dockable panels, kanban boards, a node editor and an AI chat component, with spring animations, light and dark themes, and right-to-left layout. The official site is this C code compiled to a web page, with 190 components you can click through one by one. The README's first screen is a finished screenshot, followed by the line "every image here was drawn in pure C with CUI."

The author, yappologistic, registered his GitHub account in February this year. He has 29 repos, batch-making "native, good-looking" desktop apps: the CD-shaped player Spun (471 stars), Sung (400+ stars), and the file manager Maia (151 stars). They share a style and were mostly written by AI. From his Persian-language tweets, a "Persian-language LLM client" library, and the fact that CUI's first outside contributor came specifically to fix Persian/Arabic text layout, I infer he's in the Iranian / Persian-speaking developer community.

Where the stars came from

DateStarsWhat happened
11-050Repo created; 104 commits pushed the same day
11-06—Author posts a pinned Persian tweet
11-07128r-lyeh, a well-known developer in the single-header C library scene, opens an issue
11-08275
11-09359Hits the HN front page that evening
11-10530 → 738Daily snapshot +171, then climbed another 200+

(Daily GitHub star-count snapshot, 11-10 same-day 738 is a live check of the GitHub page.)

Wave one: a contrast-based hook in the home-language community. On Nov 6, the author pinned a Persian tweet on X: "My whole UI library is smaller than your avatar pictures 😌 240 KB, 150 components, pure C, Win / Mac / Linux," with a link to the site. It reached about 43k views, 1 thousand likes, and 63 reposts. He had only 2,190 followers, and his other tweets usually get a few hundred to two or three thousand views, so this one was one to two orders of magnitude higher. The same day, people opened 6 feature requests and 2 right-to-left layout issues.

Wave two: spreading among C developers. From 11-07 to 11-08, stars went from 128 to 275, before HN. I couldn't find which post or group spread it, but people like r-lyeh were already asking for single-file packaging and an SDL3 backend.

Wave three: the HN front page and the wave of reposts after it. The HN night brought in about 250 stars (estimate: 21:54 comments mention 611 stars, the same-day snapshot shows 359). Afterward, daily.dev, HN bot accounts, aggregator sites that auto-translated it into German, Portuguese and Spanish, a Chinese "CUI tutorial," and two YouTube auto-narrated videos appeared one after another. Chinese users started asking in the repo "does it support Chinese?" and "does it run on Android?"

I found no Product Hunt listing, no big-name tweets, and no paid promotion.

Why this one: the C slot has been empty

There are plenty of UI libraries for C, but none that are "many components and look finished out of the box":

ProjectStars (11-10)How CUI differs
Dear ImGui77kBenchmark, but in C++; its default look resembles a debug panel
LVGL25kAimed at microcontrollers and mature; some on HN say CUI "looks a lot like LVGL, but prettier"
Clay18kLayout only, no components or drawing
Nuklear11.5kAlso pure C with zero dependencies, but fewer components and dated looks
microui6,900A minimal core of about a thousand lines; components have to be written yourself
raygui5,300Tied to raylib, aimed at games
Raven2,100A C UI library that just took off in October, describing interfaces in XML; components and demos are weaker

The reason is easy to guess: hand-writing 190 decent components in C is a several-people, several-years job, and the picture isn't money, so nobody did it. AI cut that cost to a few days. CUI is the first to actually do it and present it well.

It also sits where two trends meet. One is "native UI, no Electron": the same week, Rust's Rune hit HN (179 points) and gained 7+ stars in 5,000 days; Go, Rust and Zig equivalents were also gaining traction in October. The other is "writing C with AI": a large share of HN comments debate whether "having a model run a memory-safety pass makes C usable again." "C + modern component library + 250 KB" set against Electron apps that routinely weigh hundreds of MB is the headline itself.

The README also reads like a seasoned developer's: it compares itself point by point with Dear ImGui, Nuklear, Qt, GTK and Electron, lists "no screen reader, no Wayland, no mobile" as limitations in a dedicated section, and says "if you need these, use Qt." Even the AI co-authorship is stated outright. On a critical audience like HN, that disarms part of the criticism up front.

Many praise it, many criticize it, few actually use it

HN criticism clusters around a few points: "this is the default style AI produces, turned into a C framework"; "writing and maintaining this kind of code is a nightmare"; "the component ID generation is too naive, dynamic UIs will probably break"; "it did nothing when I tapped on my phone"; "I touched the node editor and the nodes flew off the screen." Someone put it more bluntly: "If it's this easy to build, couldn't I just prompt one myself when I need it?"

The praise is also specific: "finally a good-looking UI framework for a low-level language, so a small tool ships at under 1 MB instead of 300 MB"; "not a critical system, it works, and it might replace LVGL." Others asked for features on the spot: a C++ binding, a Lua interactive environment, and whether it runs on ESP32.

But look at real usage: in 5 days it shipped 4 releases, and the prebuilt release attachments were downloaded only about 108 times in total (GitHub release stats, 11-10). On Windows, someone has already reported a compile failure with the single-file build. Far more people are looking than using. Whether it can still add dozens of stars a day after the hype fades is unclear.

No copycats yet: since 11-05, the only UI component library created after that date with 20+ stars is this one. The closest approach is September's Ely-GPUI-Components (Rust, also every component clickable in the browser), which only got 600 stars.

If it were you

Verdict: Worth a shot, the cost is low. But don't expect copying one library to get you the same stars. CUI's stars came from being "the first" and from the contrast, and you can't copy either of those. What you can copy is the method: find a gap where hand-building is very expensive and AI generation is nearly free, and make the demo something people want to click right away.

Who it suits: Developers fluent with Claude Code / Codex who can generate a large library in a week and still read it and fix it; people with some connections in a language or hardware circle (native-language communities, embedded, a niche language's community).

Who it doesn't suit: Anyone building a "Rust / Go version of CUI". Those languages already have GPUI component libraries, Fyne, Gio, and similar mature options, and on HN people are already mocking it: "wait for the vibecoded Rust version." Also anyone who won't maintain it and just wants one wave of attention. HN is turning against this kind of project, and the later you post, the more you get roasted.

How to do it:

  1. Pick a gap, with the standard being "this circle has no strong, polished component library, and hand-building one is costly." CUI's comments already hint at a few: shadcn-style component libraries for embedded screens (a rival to LVGL, someone asking about ESP32, and someone already building something similar for an old Fujifilm camera), Lua / C++ bindings, and versions that actually work with touchscreens and Chinese input. If you switch languages, first check whether that language's community already has one. If it does, switch.
  2. Compile every component into a web page on GitHub Pages where each one is clickable. Put a finished-product screenshot at the top of the README, stating "all rendered by this library." Ship prebuilt examples for all three platforms. On HN someone immediately asked "are there compiled examples?"
  3. State the limitations up front in the README, compare honestly with mature options, and say plainly that AI wrote it. If you hide it, someone will dig it out of the commit history.
  4. Fix what CUI got criticized for first: usable with taps on mobile, no ID collisions, builds on Windows. That is the only place you can pull ahead of it.
  5. Release every day in the first week and reply to issues the same day.

How to get users: Start by posting a contrast-driven line in the small circle you know best (CUI's was "smaller than your profile picture"; an account with 2K followers got 40K views), and collect your first stars and issues. Better still, let someone in that circle carry it to HN or the C / embedded boards on Reddit themselves. Submitting it yourself gets you questioned in the comments.

When to get in: As early as possible, ideally before the end of 2026. "AI-generated large libraries" still feel fresh now. HN is already asking for a bar to be set for new projects, and once these pile up, the same demo won't win the same attention.

Signs you've misread it: If your library gets fewer than 200 stars in the target circle within two weeks, or the comments are almost all "another vibecoded one" with nobody discussing whether it's usable, the novelty has passed. Conversely, if CUI is still gaining dozens of stars a day a month later, release downloads are clearly growing, and people are building real apps with it, the demand is real and not just spectator interest. Then it's worth seriously building a long-maintained version aimed at the areas it doesn't cover: embedded, touch, Chinese input.

GitHub repo ↗

Research notes: competitor table, acquisition evidence, full research report
Competitors
NameWhereLaunchedScaleHow it differs from this one
Dear ImGuiOpen source201477.0k starC++, used for debug and tool panels, with a default look like a dev tool. CUI is pure C, looks like a finished app, and includes its own window layer.
NuklearOpen source2015 / 201911.5K stars (the old library: 14.0K)Also C, immediate mode, zero dependencies, but fewer components and an older look. CUI has an order of magnitude more components, plus animation and themes.
microuiOpen source20186.9k starA minimal core where you write your own components. CUI is all-in-one.
rayguiOpen source20165.3k starBinds raylib, mainly for games.
ClayOpen source2024-0718.4k starLayout only, no components or rendering. CUI includes everything.
LVGLOpen source201625.1k starTargets embedded MCUs and is mature. CUI targets desktop and WASM.
libui / libui-ngOpen source2015 / 202210.9k / 0.9k starWraps native system controls with few components. CUI draws all its components itself.
RavenOpen source2026-10-092.1k stars, 10-28 +700 in one dayThe closest recent C GUI peer. Describes UIs in XML and offers multi-language bindings, aimed at editors. CUI is stronger in component count and online demos.
Rune(anomalyco)Open source2026-10-225.9K stars, +7 in the last 5,290 days; HN 11-06 points, 179 commentsA native GPU UI framework that blew up the same week, written in Rust and backed by a well-known team. CUI is a solo project in C.
mygo / longbridge nsh / nanouiOpen source2026-09 to 105.7k / 2.3k / 0.9k starGo / Rust / Zig versions from the same "native UI, no Electron" wave.
Qt / GTK / wxWidgetsOpen source1990 eraIndustry standardMature, with accessibility and IME support. CUI admits in its README that it can't match this, and its pitch is small and good-looking.
Electron / TauriOpen source2013 / 2019MainstreamRequires shipping a browser or WebView. For comparison, CUI is 250 KB.
Where users come from
  • Verified the author's Persian X circle: the pinned tweet from 11-06 reads "my whole UI library is smaller than your profile pictures, 240 KB, 150 components, pure C", with 28 replies, 63 reposts, about 1K likes, and 43K views. His other tweets get a few hundred to 2.7K views.
  • Inferred C developer word of mouth (before HN): from 11-07 to 11-08 stars went from 128 to 275; r-lyeh, a developer of single-header C libraries, opened issue #10 at 11-07. I could not find which specific post or group spread it.
  • Verified Hacker News front page: at 2026-11-09 19:35 UTC, hilti (a long-time user who builds a Dear ImGui Mac app, apparently unrelated to the author) submitted the official site. It got 162 points / 86 comments. Two hours later, a comment mentioned it already had 611 stars.
  • Verified HN aggregators and auto-reposts: betterhn50, an r/hackernews mirror, daily.dev, LavX News in four languages, technology-times, zerodaily, a Chinese AI Tools Hub tutorial, auto-generated YouTube commentary, and DeepWiki. Afterwards, Chinese-speaking users appeared with issue #14 / #15.
  • Verified WASM online demo and README: all 190 components on the official site are clickable in the browser. The README's top section is a finished-product screenshot, with side-by-side comparisons against ImGui / Qt / Electron.

Why CUI (yappologistic/CUI) took off

Channel: GitHub; research date 2026-11-10. Data comes from our data cards, our github library (repo_day / repo_profile), live GitHub API queries, and the HN Algolia API. Web searches used Jina / Exa / Brave. The author's X profile was read via r.jina.ai.

One line

CUI is an immediate-mode UI library written in C99, with about 190 components (data tables, charts, code editor, dockable panels, kanban boards, and AI chat components), zero dependencies, a complete app in about 250 KB, support for Win32 / Cocoa / X11, and a WebAssembly build. 206 of the library's 217 commits carry Co-Authored-By: Claude Opus 5.5, and the README openly says "most of the code was written by AI under the maintainer's direction."

This is how it took off: first it got traction in the author's Persian X circle (the pinned tweet got about 43K views and 1K likes). Then a long-time HN user who builds a Mac app with Dear ImGui posted the site to the HN front page (162 points / 86 comments), and daily.dev and a batch of HN aggregators reposted it. What really hooked people was "C now has a shadcn-style component library with a finished-product feel, and every component is clickable right in the browser". Existing C libraries are either bare (Nuklear, microui, raygui), layout-only (Clay), or C++ and look like debug panels (Dear ImGui). On the other side, much of the HN comment section is arguing "4 days old, all written by Claude," and it's still unclear whether people will stick around.

1. Basic data

  • Created on 2026-11-05 08:18. It had 104 commits that same day, and the first commit, "Core engine: layout, draw list, text, theme, software renderer," landed on 09:01. That suggests the code was generated locally first and then pushed in batches. By 11-10 there were 217 commits in total: 206 from Claude, 9 from Omid Saadat, and 2 from the author (GitHub API).
  • Star curve (repo_day snapshots from our github library): 11-07 128 → 11-08 275 → 11-09 359 → 11-10 530 (+171 in a single day). 11-10 A live GitHub API query shows 735 stars, 40 forks, and 12 open issues.
  • At 11-09 21:54 UTC, someone in the HN comments was already asking how a 5-day-old C project could have 611 stars. So the HN post (posted 19:35) probably brought in about 250 stars over its first two-plus hours. Our library snapshots came later and are coarser.
  • Releases: v1.1.0 (11-07), v1.2.0 (11-09), v1.3.0 / v1.3.1 (11-09 to 11-10). Cumulative asset downloads are only about 108 (GitHub API). Far more people looked at it than actually used the downloads.
  • Code size: about 4.0 MB of C (GitHub languages API), plus a docs site in JS / CSS and utility scripts in Python. CI has 19 jobs covering three platforms, a fuzzer, and ASan / UBSan (per the README).
  • The author, yappologistic: on X as @Yappologistic "E Gurl", 2,190 followers, joined 2024-11. On GitHub, the account was created 2026-02, has 203 followers, and 29 repos. He makes batches of "native, good-looking" desktop apps and Codex plugins: Spun (a CD-style music player, 471 stars), Sung (469 / 440), Maia (a file manager, 151), Nala, Ava, Wineel, winotch, and others. They share a consistent style and are mostly AI-generated. From his Persian tweets, the nimruz-desktop repo ("an LLM client for Persian UI"), and contributor omid3098 adding Persian / Arabic text shaping and RTL support specifically to CUI, he appears to be part of the Iranian / Persian developer community (inferred).

2. Competitors: C / native UI component libraries

NameFormLaunchedScale (GitHub API, 11-10)How it differs from CUI
Dear ImGuiOpen-source C++201477.0k starThe benchmark for immediate mode, but it's C++, mainly used for debug and tool panels, with a default look like a dev tool. CUI is pure C, styled like a finished app, and creates its own window.
NuklearOpen-source C single-header2015 / 201911.5K (the older library vurtun/nuklear: 14.0K)Also C, immediate mode, zero dependencies, but fewer components and an older look. CUI has an order of magnitude more components, plus animation and themes.
microuiOpen-source C20186.9kA minimal library of about 1,100 lines where you build your own components. CUI is the opposite: all-in-one.
rayguiOpen-source C20165.3kBinds raylib, mainly for games.
ClayOpen-source C2024-0718.4kOnly high-performance layout, with no components or rendering. CUI covers layout, components, rendering, and windowing.
LVGLOpen-source C201625.1kA mature library for embedded MCUs. On HN someone said CUI "looks a lot like LVGL, but prettier."
libui / libui-ngOpen-source C2015 / 202210.9k / 0.9kWraps system-native controls. It is truly native, but has few components.
LCUIOpen-source C20124.4kA C UI library that uses CSS / XML, following a web-style development approach.
RavenOpen-source C2026-10-092.1K stars (10-28 with +700 in a single day, per the github library)The closest direct peer: a multithreaded C GUI library that describes UIs in XML, offers multi-language bindings, and also has AI co-authored commits. CUI is stronger in component count and presentation.
Rune(anomalyco)Open source Rust2026-10-225.9K, +7 in the last 5,290 days; HN 11-06 points, 179 commentsA "native GPU UI framework" that blew up the same week, backed by a well-known team and written in Rust. CUI is a solo project in C.
mygo / longbridge nsh / nanouiOpen-source Go / Rust / Zig2026-09 to 105.7k / 2.3k / 0.9kVersions in other languages from the same "native UI, no Electron" wave.
gpui-component / Ely-GPUI-ComponentsOpen source Rust2024 / 2026-0920.1k / 0.6kComponent library on Rust's GPUI. Ely uses the same playbook as CUI, with every component runnable in the browser.
Qt / GTK / wxWidgetsOpen-source / commercial C++, C1990 eraBig-company level of maturityNo accessibility or input-method support, and CUI's own README admits it falls short on these
Electron / TauriOpen source—MainstreamCUI compares itself against them with "250 KB, no WebView2"

Verdict: a pure-C library with 100+ components, a modern Web-component-library look (shadcn-style), running on three desktop platforms plus WASM, didn't exist before. The spot was empty because hand-writing it costs too much, so nobody did it. CUI uses AI to wipe out that cost.

3. Growth: how people arrived (by time)

  1. 11-06 Persian-language X circle (confirmed). The author's pinned tweet (in Persian) reads: "My whole UI library is smaller than your avatar images 😌 240 KB, 150 components, pure C, Win / Mac / Linux", with a link to the website. It has 28 replies, 63 reposts, about 1K likes, 43K views (read via r.jina.ai from x.com/Yappologistic). That's two orders of magnitude above his other tweets: his English tweet 11-08 got 2.7K views, and the CUI 1.3 launch tweet by 11-10 got 527 views. 11-06 That day it also brought in 6 feature-request issues (fazi-gondal) and 2 RTL issues (omid3098).
  2. 11-07 to 11-08 C-circle word of mouth (partly confirmed). r-lyeh, a known single-header C library developer, 11-07 opened issue #10 (requesting an amalgamation + SDL3 backend). Stars went from 128 to 275, which suggests HN had already spread it among C developers. I couldn't find which thread or group was spreading it.
  3. 11-09 19:35 UTC HN front page (confirmed, the biggest wave). The submitter hilti is a long-time HN user (karma 485) who previously posted "How I got a Dear ImGui App Approved on the Mac App Store" and several Show HNs for his own Mac tools. Nothing links him to the author; it looks like an organic submission. The post hit 162 points and 86 comments (HN Algolia), placing near the top of that day's hckrnews.
  4. Automatic reposts after HN (confirmed). betterhn50 (the HN bot on X), an r/hackernews mirror, daily.dev, LavX News (auto-generated pieces in English, German, Portuguese, and Spanish), technology-times, zerodaily, normalscience, hn.urlbox, a machucavalley blog, and a Chinese site "AI Tools Hub" that wrote a "CUI tutorial." There are also two auto-narrated YouTube videos and a DeepWiki page. After 11-09, Chinese-speaking users started filing issues: #14 "can support Android and wasm?", #15 "Can CUI support Chinese?", #16.
  5. Channels I didn't find: Product Hunt, big-name tweets, paid promotion, and the original Reddit programming-subreddit post all turned up nothing. The x-radar local corpus doesn't mention this library either.

4. Why it took off

  • The presentation grabs attention. The website is the same C code compiled to WASM, with 190 components you can click through one by one. The README's first screen is a shadcn-style finished screenshot, captioned "every image is drawn by CUI in pure C." The top HN comments: "looks really sweet," "Looks like ShadCN. That too in C. It's really really elegant," "Clearly vibecoded, but it looks really nice."
  • The contrast makes the headline. "C" plus "modern component library" plus "250 KB", while Electron easily runs 100 MB+. The author's tweet leans on exactly that gap: "smaller than your avatar", "no WebView needed2", "C99 code still compiles after 2046 years".
  • The README is restrained, like something written by a veteran. It compares itself head-on with Dear ImGui / Nuklear / Qt / GTK / Electron, lists "no screen reader, no Wayland, no mobile" under Limitations, and says "use Qt if you need those." That lowers HN readers' guard and keeps the discussion on "how good does it look and how was it generated," not "is this star-farming."
  • Zero-friction trial. Try it in the browser; the three-platform releases include prebuilt examples; you can drop it in via CMake FetchContent or just two files (cui.h / cui.c). Someone on HN asked whether there were prebuilt examples, and the answer was yes.
  • Timing. The same week, "native UI, no Electron" is picking up steam: Rune 11-06 hit HN (179 points), +5,290 stars in one week; mygo, nsh and Raven all picked up traction in October. Another thread: AI writing C. HN comments are discussing "now that Fable does memory-safety checks, C is worth caring about again." CUI sits right at the intersection of the two.
  • The author already had a small community. 2,190 followers, mostly Persian-speaking developers. Earlier projects Spun and Sung each had four or five hundred stars, and those people supplied the first 43K views.

5. Differentiation, and whether that's why it took off

The differentiation rests on four things: pure C99 with zero dependencies; component count and a finished look (about 190 components, including data grids, charts, a code editor, dock panels, dev tools, and AI chat components); animation, light and dark themes, and RTL; and a WASM live demo for every component. No other C library combines all of these. That's why it got reposted: nearly every comment praising it landed on "looks great, shadcn-like, in C."

But the differentiation rests on "AI generates it all at once," which others can easily replicate. One HN commenter put it bluntly: "If it's this easy to build, I'll just prompt one tailored to my needs." So it's a presentation difference, not a technical moat. Whether it keeps users depends on whether the author can fix the issues that follow (Windows amalgamation build failures, i18n, Chinese, 74 MB memory use).

6. Visibility and copycats

  • Visibility: spreading within developer circles. It reached the HN front page (162 points), was reposted by daily.dev and a dozen HN aggregator / auto-translation sites, and the author's Persian tweet drew 43K views. No big-name tweets, no mainstream tech coverage. Comment reception is split: the look gets praise, "vibecoded" draws skepticism, and on X someone pointed out the author has "only two merge commits."
  • Followers: none yet. Among GitHub repos created after 11-05 with ≥20 stars, the only "UI component library / GUI library" is CUI itself. A close predecessor is Ely-GPUI-Components (2026-09, Rust, every component runnable in a browser), but it came before CUI.

7. Takeaways

  • Pick an empty spot where hand-writing is extremely costly and AI generation is cheap. For example, a comprehensive, finished-looking component library for an obscure but hardcore language (C, Zig, Odin, Fortran), where the visuals themselves create the contrast.
  • Presentation matters more than code. Compile every component to WASM on GitHub Pages so each one is clickable; put a finished screenshot on the README's first screen, captioned "all rendered by this library"; ship prebuilt examples for three platforms so people can try it without installing a compiler.
  • The README admits its weak points upfront. A clear Limitations section, honest comparisons with mature options, and public disclosure of AI co-authorship disarm skeptics in a tough community like HN.
  • Start in a native-language circle, then go to English communities. Launch in the home-language developer circle with a contrast hook ("smaller than your profile pic") to collect the first stars and issues; then let others submit it to HN on their own, which can add several hundred stars in a day.
  • Release frequently in the first few days. 5 days, 4 releases, and responding to issues every day make onlookers feel "this project is alive."

8. Still unclear

  • Couldn't find which post or group the 150-star one from 11-07 to 11-08 came from (r/C_Programming, Telegram, Discord?). The original post is missing.
  • Whether the author arranged for hilti to submit to HN. Current evidence says it was organic: he's a Mac developer working with Dear ImGui, and the topic fits his interests.
  • Whether the two YouTube explainer videos were posted by the author, or are auto-generated content channels.
  • The release has only about 108 downloads, so real usage is small. Whether it can sustain dozens of stars a day after the HN spike is uncertain. The star timing can't be pulled: the GitHub stargazers endpoint returned 404 this time, so hourly verification wasn't possible.
  • Code quality: some on HN question whether widget ID generation is too naive and whether dynamic UIs may break; there are already reports of Windows amalgamation build failures (#17).

Sources

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.