Uno: Create Beautiful Cross Platform .NET Apps Faster

Original Article ↗ Hacker News Discussion ↗

A cross‑platform .NET UI framework called Uno Platform is drawing interest as an alternative to Microsoft’s shifting desktop GUI story, promising pixel‑perfect apps across Windows, mobile, web and Linux using C# and XAML. Commenters praise its flexibility, WebAssembly support and open‑source Apache 2.0 licensing, but raise familiar concerns about cross‑platform trade‑offs, incomplete platform parity, and the long‑term sustainability of tooling vendors. Comparisons with Avalonia, MAUI, Flutter and Electron highlight a wider frustration: despite many attempts, .NET still lacks a clear, stable “gold standard” for modern, native‑feeling cross‑platform desktop and mobile apps.

Positioning & Architecture

  • Uno is a .NET/C#/XAML cross‑platform UI framework targeting Windows, iOS, Android, WebAssembly, macOS, and Linux.
  • It uses native UI stacks where possible: UIKit (iOS), Android Views, WinUI/UWP on Windows, HTML DOM on the web, and a Skia-based renderer on Linux via X11.
  • Apps can embed platform‑native controls on most targets; Linux is Skia-only, so no embedding of native Linux widgets.

UI Philosophy: Native vs “Pixel Perfect”

  • Default goal is “pixel‑perfect” identical look and behavior across platforms, closer to Flutter than to “pure native” look-and-feel.
  • Built-in themes: Material, Fluent, Cupertino, plus full styling/control template customization.
  • Web output is DOM-based (not canvas), so browser features like search work; text selection is disabled by default to mimic WinUI but can be enabled.
  • Some commenters report non‑native behavior on Linux/Web and find that approach less compelling.

Comparisons: Avalonia, MAUI, Xamarin, Others

  • Uno is often compared with Avalonia and MAUI/Xamarin.Forms.
  • Several commenters consider Avalonia the current “gold standard” for .NET cross‑platform: more WPF‑like, more powerful bindings, richer feature set, and fewer behavioral differences between platforms.
  • One detailed comparison claims Avalonia has many features missing in Uno/MAUI and is easier for WPF developers, though others note Avalonia gaps (no WebView, slow TextEditor).
  • MAUI is widely described as “not ready” or “half‑baked” for serious work; WPF is still praised as the most productive and stable for Windows‑only.

Developer Experience & Tooling

  • No visual WYSIWYG editor yet; Hot Reload is said to work well.
  • XAML is prominent in marketing and seen by some as off‑puttingly verbose; others note C#‑only markup options and say you can avoid XAML.
  • Documentation is perceived as improved but still with sparse areas; past experiences mention partially implemented features and styling friction.
  • Uno exposes additional “platform” pieces: navigation/auth/logging/DI recipes, toolkit controls, and C# markup, all positioned as FOSS.

Licensing & Sustainability

  • Core Uno is Apache 2.0; toolkit repo is MIT, but marketing copy suggests revenue-based licensing for the toolkit, causing some confusion.
  • Monetization: paid support plus commercial products (e.g., a Figma design‑to‑code plugin).
  • Project leadership states the framework will remain FOSS and revenue will come from productivity tooling.
  • Some commenters are wary due to recent OSS “license rugpulls” and plan to adopt Uno cautiously.

Broader Cross‑Platform Skepticism

  • Several participants argue cross‑platform UI frameworks systematically underdeliver, with maintenance pain, dependency chains, and fragility around OS updates.
  • One view labels cross‑platform promises as effectively a “scam,” especially for mobile; others agree there are always tradeoffs but note that some stacks (e.g., Flutter) behave better than others.