Desktop

Looking to expedite the cross platform development process? Uno Platform offers this and much, much more. In fact, here are 50 reasons why exactly you should use it for your next development project.   It is Open Source and Free – under Apache 2.0   It is mature and battle-tested on hundreds of apps built over the past 6 years  It can help port code from 20 years ago to iOS, Android and Web – like we did with the Windows Calculator  It allows you to leverage your existing C# and XAML skill set to build apps for iOS, Android and Web  One codebase – 4 different platforms – need we say more? (iOS, Android, Windows, WebAssembly)   It supports Progressive Web Apps (PWA)  It is professionally supported – if you require professional support  It gives back to the community – not only the code but it supports other OSS projects, user groups and conferences  You can make a gradient brush  Never write Objective-C again  Reuse your favorite MVVM pattern on all platforms  XAML for UI is a mature & well documented technology – you’ll always find an example suiting your needs  Start developing your app before knowing which platform you’ll need to target  Reduce the pressure on your designers

When we initially open sourced Uno Framework at //build 2018, we took a big step in showing the world what we had been internally working on for nearly five years. The year was 2018 and we were still doing mostly mobile work via UWP.  During those days, you saw us fly the #UWPEverywhere banner proudly. A lot has changed since then in the .NET ecosystem, in WebAssembly world, as well as in scenarios our community had been asking us to cover. While UWP was, and still is, our first love, with today’s announcements we are keeping pace with our audience asks and we are shifting gears towards ensuring the future WinUI stack can be run everywhere – WebAssembly, iOS, Android, and of course Windows, making room for our new northern light – #WinUIEverywhere!!!  In practice, what does that mean? Announcing XAML Hot Reload for Uno Platform Preview The inner loop for developing with Uno gives you the ability to use XAML Hot Reload in Visual Studio for Windows, allowing you to go to 95% of your app’s development. You generally need to finalize your application’s testing using the actual app environment, on device or in a browser.  The ability to Hot Reload XAML from Visual Studio while the app is running, will give for the ability to update the

By now you may have heard about Uno. In this post series, I want to lay bare Uno’s technical innards. We’ll look at the critical code that powers the platform, and chart the ups and downs of building a UI platform. First, let’s get the lay of the land. The Uno Stack Uno is a cross-platform UI framework. You write an app in C# and UWP-flavoured XAML markup. It runs on Windows because it’s a UWP app. With Uno, it runs on Android, iOS, and (for the brave) in the browser via WebAssembly as well. I drew a neat sketch of the tech stack. On iOS and Android, Uno uses Xamarin to access the platform’s native framework. In the web version, it’s running directly on top of Mono, which in turn is running on top of WebAssembly. So what’s Uno doing? There are a few things that need to be done to get your app running: -At compile time, Uno parses XAML files into C# code, creating the information needed to build the app’s visual tree; -It implements a complete DataBinding engine, optimized for static type-checking where possible; -It implements the views and controls in the UWP framework, using each platform’s native UI framework as a basis. Each of those items warrants