HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
AvaloniaUI
Avalonia
C#2014–2025
AvaloniaUI / Avalonia

Avalonia

Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The future of .NET UI

62Distinct people
79Mentions
2Explicit recommenders
31.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The future of .NET UI

GitHub

Where it is used

  • ILSpy — ILSpy uses Avalonia to build its cross-platform desktop UI for Windows, Linux, and macOS. Source
  • Wasabi Wallet — Wasabi Wallet uses the Avalonia framework to build its cross-platform desktop application for Windows, macOS, and Linux. Source

What people are saying

Showcase of apps built with avalonia: https://github.com/AvaloniaUI/Avalonia#showcase Saw this update for Avalonia that I wanted to share, since the prospects of the new…

banashark used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year79 dated mentions

Observed mentions: 2014-09-08 22:02:04 UTC to 2025-07-30 18:52:08 UTC.

0510152014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC431
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC523
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC817
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC13013
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC10010
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC10010
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC909
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC523
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC826
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC413

What Hacker News says

9 sources
Here are some differences I was able to find: - Uno uses the UWP API and XAML, whereas Avalonia uses a derivative of WPF - Uno renders using the underlying platform, uses native controls whenever possible, particularly for input controls. Avalonia focuses on using its controls, not native ones (although support for native controls is WIP I think) - Uno is based on WinUI, so in theory WinUI components should be usable in Uno apps - Uno supports WebAssembly, but not Linux and MacOS natively Links: - https://github.com/unoplatform/uno/issues/17 - https://github.com/AvaloniaUI/Avalonia/issues/587
In Uno: Single-Codebase for Windows, WebAssembly, iOS, macOS, Android and Linux
> license for that kind of devices is quite shady Would you please describe what exactly is shady in the licensing for someone looking at Qt? My bigger issue is that they are inflexible with their licenses for small businesses. Either you use LGPL, which requires copyleft on bundled mobile apps (I believe) or you pay based on the total revenue of your business, no matter how small the app is, as told by Michael Dominick on the Coder Radio podcast. Can be quick expensive if you want to launch a new product line, as Mike did. He decided to rewrite his app in C# and AvaloniaUI for Windows/Linux cross platform support. https://github.com/AvaloniaUI/Avalonia > that they have a clear history to do major breaking changes at each major release This is a major issue for me.
In What's New with Qt for Android

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.