Uno Platform Part 1

The Discussion

• 

  This is awesome!
  Things are looking very good.
  I can only imagine all this running with WinUI and .NET 5

• 

  Uno platform is the big thing we were awaiting for 8 years, since the death of Silverlight. Now Uno presents a model way more powerful using WebAssembly and native Windows, Android iOS development!

• 

  @TonyHenrique:

• 

  I switched to Xamarin to do cross platform. With this, I can stick with UWP XAML.

• 

  This really is awesome!

• 

  OK I have been investing into Xamarin for C# Android Apps development. But I do miss Silverlight Web Applications. So this is looking pretty cool, if Microsoft keep its development commitment here.
  Will be very interested in the UI Widgets and Tools available out of the box, or will we have to wait for (compelling) third party controls.

• 

  @Jules:
  
  The Uno team maintains a port of the Windows Community Toolkit that works on all supported platforms, so you should be covered.

• 

  @Jules regarding third party controls and more advanced demos, please stay tuned for the second part of this video, there is a lot more demos :-)

• 

  @Yong:
  Plus you get to deploy your app as a website!

• 

  Love the concept. Tried the Android "Uno Gallery" app it is a bit laggy. If Uno is adding Web Assembly to what Xamarin Forms already offers, why not just add Web Assembly support in Xamarin Forms? With Uno and Xamarin Forms we now have two flavors of XAML.
  
  The Uno Architecture (https://platform.uno/how-it-works/) seems to have one more layer compared to Xamarin Forms.
  
  Would really like to see the same app build and profiled with Xamarin Forms and Uno and see how they match up (performance, executable size, etc.)
  
  Looking forward to watching Part 2

• 

  @Marcelo:
  
  The Uno Gallery app is actually running a quite older version of Uno Platform, so it is possible there have been many improvements since. Also for Android, there is an active issue on GitHub with plans to look into the XAML performance there, there is room for improvement.
  
  For WASM support on XF, it is actually much easier to utilize Uno, as support for multiple platforms on XF is clearly hard (UWP is already lagging a bit behind Android and iOS) so having another one would be even harder. Thanks to the fact Uno has the exact same API as UWP, it is just possible to reuse the existing UWP renderers, which is great. There have always been multiple XAML dialects (WPF, UWP, XF), Uno doesn't luckily add a new one, instead it just reuses the UWP one. And seeing UWP will evolve to WinUI as the new default UI framework on Windows, it should be a great choice - we will then have just to flavors - UWP(WinUI, Uno) and XF. The XF XAML is and will be different going forward unfortunately, as it would be a very siginificant breaking change, but I think it is fine - the two versions can influence and inspire each other.
  
  Uno should be on the same level as XF architecture-wise, which layer do you mean?

• 

  🦙 Link to Part 2: https://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Uno-Platform-Part-2

• 

  This is awesome thanks!