Status of WinUI 3 Renderer — Request for roadmap and support clarification

[dmarinom]

Status of AdaptiveCards.Rendering.WinUI3 — Is the WinUI 3 renderer still actively supported?

Hello team,

I'm currently maintaining a production-level project built on WinUI 3, which integrates the AdaptiveCards.Rendering.WinUI3 package. I chose this technology based on Microsoft's strategic direction for modern desktop development via the Windows App SDK.

However, I've observed the following:

• The latest NuGet release (2.2.3-beta) dates back several months, with no recent updates.
• GitHub activity related to the WinUI 3 renderer appears minimal, and there are no active milestones or roadmap items.
• Key features available in other renderers (e.g., Carousel, SVG background support) are either missing or undocumented in the WinUI 3 implementation.
• The project structure suggests a parallel development path for WinUI 3 (source/uwp/winui3/), but it seems to be in maintenance mode.

Questions:

• Is the WinUI 3 renderer still under active development or considered stable?
• Are there plans to move it beyond beta and align it with the feature set of other platforms?
• Is WinUI 3 still considered a strategic platform for Adaptive Cards going forward?
• If not, what alternatives would Microsoft recommend for developers who have already invested in WinUI 3?

This is not a complaint — rather, a request for clarity. Many developers have adopted WinUI 3 based on Microsoft's guidance, and we would greatly appreciate transparency regarding the future of this renderer.

If the project is open to community contributions, I’d be happy to explore ways to help improve or extend the renderer.

Thank you!

Diego Monetti