Day 5

Hours worked/Total: 1/9.5

Day Recap

Outcome: Spent the day researching options for truly native Windows development. Explored various technologies like C++, C#, .NET MAUI, WinUI3, and Avalonia, but each has its own pros and cons, making the decision tougher.

What I Did

• Researched native Windows development alternatives:
  • C++: Core language for Windows apps but steep learning curve.
  • C# with .NET:
    • MAUI: Cross-platform and modern but still uses WinUI3 under the hood.
    • WPF and WinForms: Both look dated and aren’t ideal for modern UIs.
• Looked into .NET MAUI:
  • It’s cross-platform but still runs on WinUI3 for Windows, which gives it a somewhat amateurish look, similar to Electron apps.
• Explored a list of professional apps built with WinUI3:
  • Apps like WhatsApp and Outlook use WinUI3 and look polished.
• However, according to Reddit discussions, WinUI3 isn’t stable or production-ready.
  • It uses XAML for layouts, and no one seems to fully adopt it yet.
• Investigated Avalonia:
  • Gaining a cult following, with references from companies like Honeywell and JP Morgan.
  • Still based on .NET, so it doesn’t escape the ecosystem’s baggage.

Remarks

Windows native development is fragmented.

C++ remains the core standard for native development, but it’s not beginner-friendly.

C# offers a more accessible path, but technologies like MAUI and WinUI3 don’t seem to be stable or polished enough for professional use—despite big apps like WhatsApp using them.

While Avalonia is gaining traction and industry validation, it still lives within the .NET world, which raises concerns about long-term stability and development overhead.

Next Goals

• Look into Avalonia