Windows 10 X : UWP neo


So, from this blog post, the death of UWP is greatly exaggerated:

The better come up with a much better story to sell this – I understand that the WinRT api is much better for power management, mobile, etc. but clearly not as rich as Win32 – and this doesn’t really explain how Xamarin fits in with all this going forward either. There’s a lot of explaining for .NET 5.0 and Windows development to make the story coherent for developers.

Comments (34)

34 responses to “Windows 10 X : UWP neo”

  1. fpalmieri

    Oh, and will apps from the Neo and Duo be able to be developed from the same code base?

    • gavinwilliams

      In reply to fpalmieri: We only know that they will be able to be in the same way as today. We have to wait for .Net 5 and new templates to allow us to deliver UWP apps using .Net 5 (.Net Core today). Things like Xamarin will continue to be a solution until then. And of course you have to consider that you may use a universal application template but the UI or other part may be platform specific and vice versa.
  2. juan

    I read that Hitler is also alive and well.

    Supposedly he is in his secret base in Antarctica plotting his return.

    Just saying.....

  3. dontbeevil

    Probably we're not going to see this news here: Rudy Huyn moved to MS to focus on UWP development

  4. dontbeevil

    For some reasons there is a personal war against UWP, but let's provide some facts:




    1- (maybe they didn't make UWP apps big and clear enough)


    2- was never mentioned the number of sessions about UWP at MS ignite, but they keep mentioning the lack of UWP sessions at PREVIOUS conferences


    3- was never mentioned for example that Adobe Fresco is UWP, but they rushed to mention that Gears5 is win32 and not UWP




    I like to end with a quote from thurrot:


    "Every year, some pretentious tech blogger has to remind his tech-infatuated (and probably Apple-loving) readers that there’s an Android update problem."


    you can just adapt this to your needs ;)

  5. the escalation

    It's dead.

    I don't get why people can't face the facts. Sure, current UWP apps will continue to exist in a void as they always have, and developers can and will update them if they see fit, but for all intents and purposes - UWP is dead. If UWP were still viable, you wouldn't have seen Microsoft go with Android for the Surface Duo.

  6. parth7878

    The UWP Dropbox app on Windows 10 and Xbox has received a new update in the Store which brings some great performance improvements and an enhanced UI inspired by Project NEON. According to the app’s developer Rudy Huyn, this app was designed to carry a transparent blurry menu on

  7. dontbeevil

    if this picture will not keep disappear from the comments for some strange reasons, it will clarify many doubts

  8. gavinwilliams

    "WinRT ... clearly not as rich as Win32 " - That's not clear to me at all anymore, considering the pace of WinRT API development. There are only 2 features now for game development that separate WinRT from Win32 ..

    1. Win32 can suspend taskbar/titlebar, UWP cannot
    2. Win32 can be distributed anywhere, UWP cannot

    PS. This is just my perspective. AAA dev's may have more differences to list. And obviously I'm not speaking for consumer and enterprise app development. But WinRT has a large coverage now, I would be surprised if there was a single productivity app I couldn't make for WinRT/UWP - For example Photoshop, 3DS Max etc could be made with WinRT/UWP given enough manpower of course

  9. ErichK

    Have to admit the software development landscape in the Microsoft and/or Windows universe does seem to be getting rather complicated lately.

  10. Paul Thurrott

    This post doesn't mention UWP at all?

    It just says what I reported, that Microsoft will explain the developer story later.

    What it does say is "Windows apps, whether they were written in the last month or five years ago." This suggests, Win32, WinForms, WPF, and UWP.

    Why does everyone have such a bug up their ass about me accurately reporting what we were told at Build?

  11. factoryoptimizr

    Microsoft's confusing developer story is beginning to take focus, though clarity is still a year or two away. .NET Core server-side and WinUI (son of UWP) UI-side. These should converge late next year in .NET 5. In the short-to-medium term, Xamarin is the cross-platform mobile solution, allowing Android & iOS development using C#/XAML (though not the "standard" flavor of XAML). Over the longer term, Blazor (or some derivative) becomes the true "unversal" cross-platform solution, enabling development of browser pages, PWAs, web apps (using WebAssembly) and, ultimately, native cross-platform development for both mobile and desktop (using the theoretical Blazor Native) -- all using C# and the UI rendering language of your choice. Interestingly, the Uno framework provides much of this capability today, using C# and standard WinUI/UWP XAML for UI. Given the participation of several heavy hitters from Microsoft Dev at last month's #UnoConf, Uno could be the dark horse that finally brings things together.

    • jules_wombat

      In reply to FactoryOptimizr:

      Exactly - its all pretty confusing and too complex picture for developers to show any interest about.

      What exactly is WinUI (son of UWP) UI-side ? is it yet a another .NET Client side UI attempt ? - Does it run on Android, Linux and in Web browsers - if not, whys should any developer start investing in yet another failed Microsoft client technology ?

      Nope. The Developers moved on long ago, after the Build 2011 fiasco.

      [n.b. I sometime attempt to develop Xamarin Android Apps, in C#, but the Visual Studio UI Emulator fails the whole UI development experience. Its really Not it for Purpose, and should be scrapped.]

    • Tony Barrett

      In reply to FactoryOptimizr:

      That could all be too late. Clarity still 'a year or two away' could be everything a developer needs to shift away from Microsoft. Besides, MS keep moving the goalposts all the time anyway - most Devs don't know where they stand, and if they invest their time, effort and money, whether MS will just throw them under a bus again as they've already done many times.

    • Usman

      In reply to FactoryOptimizr:

      Uno apps ported to other platforms are great, but it is absolutely horrible for a web use case. It's a technical marvel, but if you were going to do a cross platform app including web, I wouldn't pick Uno.

      The way they've implemented web assembly is ridiculously slow and unless its enterpise where users have a fast internet connection are expected to wait 30-40 seconds for the initial page load when downloading 6MB mono runtime in web assembly.

      The Windows 10 calculator in Uno for web is a whopping 50 MBs and takes 22seconds to initially load on a gigabit connection and a high end i7 machine ( )

  12. ghostrider

    MS can carry on as long as they want with UWP - it's just their customers, users and developers who aren't using it. The MS app store is still barren, 98% of WIndows users still sit in a browser (usually Chrome) and any apps they do use are win32. Don't forget, UWP has been around since 2012 in one form or another, and it's gone pretty much... nowhere. The primary reason is, it was developed for mobile - the desktop just happened to be able to run the apps as well, but on the desktop, they don't have much real point.