xtd: Modern C++20 GUI Framework That Feels Like WinForms

You're writing C++20 coroutines and modules in one file, then switching to Qt's signal-slot syntax from 1995 in the next. The cognitive dissonance hits every time you open a GUI component. Qt shipped its first release when Netscape Navigator dominated browsers. wxWidgets predates it by three years. These frameworks work, but they carry design decisions from an era when C++ didn't have auto, lambdas, or move semantics.

The Desktop C++ Developer's Dilemma

C++ developers face an uncomfortable choice: stick with GUI frameworks that predate modern C++ language features, or abandon native code for Electron and accept the 200MB memory overhead. Qt and wxWidgets deliver cross-platform compatibility, but their APIs reflect 1990s design patterns. You write clean C++20 code for your business logic, then context-switch to framework APIs that feel like archaeological artifacts.

The web revolution left desktop C++ developers behind. Teams building native applications watch JavaScript developers spin up cross-platform UIs in minutes while they wrestle with platform quirks hidden behind abstraction layers designed before the iPhone existed. Refusing to give up native performance shouldn't mean accepting outdated tooling.

What xtd Actually Is

xtd is a C++20 framework providing three components: console applications (xtd.core), GUI forms (xtd.forms), and unit testing (xtd.tunit). The framework takes design inspiration from .NET's WinForms API, translating that programming model into modern C++20.

Rather than reimplementing GUI rendering from scratch, xtd wraps platform-native libraries—Win32 on Windows, GTK on Linux, AppKit on macOS. The framework acts as a unified API layer over existing technologies. The current version 0.2.0 requires C++20 as the minimum standard, signaling commitment to modern language features over backward compatibility.

The project sits firmly in pre-1.0 territory. Version 0.1.1 shipped in July 2023, followed by 0.1.2 in March 2024, with 0.2.0 development continuing as of November 2025.

The WinForms API in C++20

The framework includes over 500 examples demonstrating the WinForms-style approach. Anyone who built Windows desktop applications in the 2000s will recognize the button-click, form-based patterns. xtd.tunit integrates with Visual Studio 2019+ Test Explorer, bringing xUnit-style testing into the same framework rather than requiring separate testing libraries.

For developers who remember when desktop development meant forms, buttons, and event handlers without JavaScript build chains, the API patterns feel familiar. Modern C++20 features work naturally with the framework—no fighting the type system to make lambdas cooperate with signal-slot macros.

Who Should (and Shouldn't) Use This

Good candidates for xtd: teams comfortable with pre-1.0 adoption risk, developers who value API clarity over maturity, projects where WinForms-style patterns align naturally with requirements.

Poor fits: enterprise projects requiring production stability guarantees, teams needing third-party widget libraries, anyone expecting Qt's documentation depth and Stack Overflow answer density. The framework carries roughly 1,100 GitHub stars—recognition in the awesome-modern-cpp curated lists, but modest adoption compared to established alternatives.

No major public enterprise users appear in search results. Active development continues, but this isn't a framework with Fortune 500 companies publicly backing it.

The Adoption Reality Check

wxWidgets forum discussions mention xtd as an alternative, indicating the framework generates comparison interest. Updates in March 2024 and November 2025 show consistent maintenance, though not rapid release cycles. The project demonstrates stable, incremental progress rather than exponential growth or viral momentum.

The framework competes directly with wxWidgets and implicitly with Qt. Betting on xtd means accepting limited third-party resources, smaller community support, and API changes before 1.0 ships.

Making the Framework Decision

Evaluate xtd against Qt and wxWidgets by weighing API ergonomics versus maturity. The tradeoff crystallizes quickly: cleaner modern C++20 API versus battle-tested stability and widget libraries.

Teams considering xtd should build prototype implementations testing framework limitations against actual requirements. Migration risk assessment matters—switching GUI frameworks mid-project approaches rewrite territory. The decision hinges on whether WinForms-style API clarity justifies pre-1.0 adoption risk for your project timeline and risk tolerance.