What changed
Until now, new controls usually showed up in the Gallery after they reached a stable Windows App SDK release. By then the APIs were mostly locked, so there was little room to change them based on feedback. Microsoft's pitch for the new model is simple. When a new experimental WinUI release ships, the Gallery can ship samples for it right away. Developers can open the app, try a control, and copy working XAML and C# into their own project.
The Gallery now targets the experimental Windows App SDK, currently 2.5.4-experimental, and ships it self-contained, so nothing extra needs installing. Microsoft's documentation lists that experimental package as released on September 29, 2026. The stable track is separate, with 2.5.1 listed as the latest stable release.
Don't confuse the names
- WinUI Gallery 3.0 is the version of the sample app.
- WinUI 3 is the UI framework developers use to build apps.
The two share a number but are different things. Windows Central also points out that the Gallery is mostly invisible to ordinary PC users.
What's in the release
The GitHub release notes for v3.0.4 list these additions:
- Windowing APIs: samples for
Window.Width,Height,MinWidth,MinHeight,MaxWidthandMaxHeight, plus window UX refinements. - Layout and paging controls:
FlowLayout,LayoutPanel,PagerControlandWrapPanel, each with an Experimental badge. - TableView: five samples for the new native TableView.
- Inking:
InkCanvasandInkToolBarsamples. - Charts: an experimental page covering line, bar and area charts, axes, markers, data labels, time series and live data.
- Search and navigation: control pages now have search tags, the no-results screen is redesigned, and mouse back/forward buttons navigate the Gallery.
- Sample catalog: every page and sample is indexed in
catalog/windows-samples.json, which the release notes describe as a catalog for tools. - Accessibility fixes: these include a Canvas slider Narrator announcement, keyboard focus traps, and color contrast in dark mode.
- Fixes: the notes list a TableView
NullReferenceExceptionin trimmed Store builds, and malformed XAML in 13 sample bundles. - Removed: the ListBox sample.
These are changes to the sample app. They don't mean any third-party app gets better accessibility or behavior automatically.
Experimental doesn't mean production-ready
Microsoft's release-channel documentation defines the three channels:
- Stable: production-ready in intent, with supported APIs.
- Preview: an early look at the next stable release that may still have breaking API changes.
- Experimental: early-stage features where APIs may change, be removed, or never ship. It is intended for exploration and feedback only, and it isn't supported.
The Gallery states the same limits. Experimental pages carry a badge in the navigation pane, and experimental samples show a warning in their source panel. Microsoft says not to use experimental APIs in production apps yet.
Practical advice
- Use the Gallery to evaluate, not to commit. Treat anything with the Experimental badge as a prototype.
- Keep experiments isolated in branches or internal tools, because API changes can force rewrites.
- Check the channel before shipping. A control shown in the Gallery may not have reached stable.
- Send feedback early. Microsoft asks for issues to be opened on the WinUI Gallery repo.
Analysis
The trade-off is that developers get earlier access and Microsoft gets earlier feedback. The cost is that people may copy experimental code without noticing the warnings. The badges and source-panel warnings are meant to reduce that risk. Microsoft's stated reasoning is that earlier feedback gives it more room to change designs before they lock. Whether it acts on that feedback is something only future stable releases will show.
One publication-status oddity is worth noting. The v3.0.4 release page was reachable, but the repository's main release list didn't show it when we checked. A third-party listing, UpdateStar, also shows 3.0.4.0 released on 10/13/2026.
For developers building Windows 11 apps, the practical result is that the Gallery now previews the controls that may reach stable later. It is not a signal that those controls are ready to ship.