Welcome to .NET Multi-Platform App UI

https://devblogs.microsoft.com/dotnet/introducing-dotnet-maui-one-codebase-many-platforms/

by taspeotis • 4 years ago

46 20 4 years ago

devblogs.microsoft.com

tumetab1• 4 years ago

It's nice to see this project coming to fruition. I just find it sad Gnome/KDE/Linux are not supported. Still there's always the possibility of doing an Electron-like app using Blazor for Linux apps.

zamalek• 4 years ago

I've been using .Net since 1.0 beta, and this is one of the major reasons that I'm planning on learning Flutter: Linux support.

banashark• 4 years ago

For those looking for a linux-compatible solution, I've had some success with Avalonia: https://avaloniaui.net/

Specifically I made a small application with F# and the FuncUI library https://github.com/fsprojects/Avalonia.FuncUI

So far the most complex real-world application I've seen is Lunacy: https://icons8.com/lunacy

It's nice to have something like this out there. It definitely eased my apprehension of using the platform on the grounds of it being immature.

I've a decent amount of experience with Xamarin (Native and Forms), and so far I've had 1/100th of the build issues with Avalonia.

I am excited to try out MAUI however and see how things have evolved!

WorldMaker• 4 years ago

There's at least one open source community project/fork trying to build a Linux backend (via GtkSharp in this case): https://github.com/jsuarezruiz/maui-linux

jeroenhd• 4 years ago

The most annoying part to me is that apparently some version of the framework support Tizen, which is just a weird version of Linux running plain old Wayland and Pulse.

I'll have to skip MAUI again because of its lack of Linux support. I guess Microsoft doesn't want the Linux plebs to use their ecosystem.

chizhik-pyzhik• 4 years ago

https://xkcd.com/927/

neonsunset• 4 years ago

Unfortunately, this XKCD post is used correctly.

.NET is known for its homogeneity and massive standard library that seems to be a black hole where eventually all good implementation of popular libraries end up in.

With one exception: UI frameworks. For whatever reason, UI frameworks have bloody and complicated history starting with early versions of .NET Framework and ending with the latest upcoming .NET 7. Let's hope, fingers crossed, this time is different :D

yakkityyak• 4 years ago

I would actually go as far as to say that even in a Microsoft-only vacuum, they have cornered themselves into this exact xkcd post.

If you are working in C#, Microsoft offers at least 5 different UI frameworks to choose from. Off the top of my head there is WinForms, WPF, UWP, WinUI, and now MAUI. All of them step over each others toes to some degree.

As far as I know, it's still impossible to write apps that can fully incorporate the late Windows 10/11 acrylic design language. WinUI 2 & UWP is basically dead, and it still seems like WinUI 3 dropped support for it.*

So if I'm a writing a new app and actually want to adopt the new design language, it still seems like you are stuck with no options.

1. https://github.com/microsoft/microsoft-ui-xaml/issues/2236

EDIT: after some further sleuthing it sort of looks like window acrylic might show up in WinUI 1.1 coming sometime this year, but it's not so clear.

metaltyphoon• 4 years ago

Until dog fooding happens, it's a hard pass. Wrote teams on electron / reactive native? Undo that and do it using MAUI. Prove to your developers it's a good stack to sink your time into.

But but... it was written years ago when MAUI wasn't a thing...

Well it is now and you have infinity money so just do it. We need high profile application to be MAUIs face.

jnash2• 4 years ago

Hard agree. 95% of Microsoft tech doesn't survive for long. Silverlight anybody?

psd1• 4 years ago

I suggest they rewrite Teams in the bin.

hbcondo714• 4 years ago

Visual Studio 2022 will GA .NET MAUI tooling support later this year

I'll wait until this at least.

bob1029• 4 years ago

I love many things about Microsoft & .NET. Most, even.

Their UI frameworks are not among these things. I don't know that they could ever be trusted again with something like this.

We do use Blazor right now, but I've already got us sliding back into a bare-ass vanilla JS solution that only uses the most minimalistic of AspNetCore APIs. I.e. connect websocket & run my own protocol on top type of deal. Blazor showed me the way (push deltas and events over websocket), but I don't like the lock-in to anything Microsoft+UI.

The open web is a much more trustworthy path. Nothing else comes close on a historical basis.

jerriep• 4 years ago

Yeah, I am with you and do not trust the longevity of any MS-related UI technology. History seems to indicate that it will either be outright killed or will die a slow death as they jump on the next shiny thing.

I love ASP.NET Core but this attitude sadly seems to have infected it as well. There's still a lot of room for improvement in MVC and Razor Pages, but these seem to be in all but maintenance mode as focus has shifted over to Blazor and Minimal APIs.

isodev2• 4 years ago

Welcome to yet another .NET inspired UI framework. They promise* it will stick around for at least a few months before the next rewrite.

jnash2• 4 years ago

It's 2022 and Microsoft is doing yet another UI framework. I wonder how many months it will be supported before it is dropped and a completely different UI framework is promoted instead? But hey don't worry! Rewrite all your important business applications in this new framework! It will be awesome! And in a few months time when it is dropped, rewriting everything again in the next new UI framework because this time it will be the one to last more than a year! Really! Surely! Trust us!

g0gzs2• 4 years ago

I see many negative comments about Microsoft and "yet another UI framework"... I started back in the Webforms/Silverlight days, and brough over my skills to each next iteration and had a pretty pleasant dev. experience ever since.

I was using the following: Silverlight -> WPF -> Windows Phone -> WPF -> Angular/webdev -> Xamarin.Forms and now since MAUI Preview 11, we've been building our new mobile/desktop product with it, and we'll release it soon.

The part where I was a web developer was honestly awful. Web frontend isn't even close to what any of those mentioned above are right now. Layouting stuff on the web is a nightmare, a little less now that grid is coming along, but still lightyears away from what you have in WPF/XF/MAUI... and then there's decoupling UI code from your business logics for testability. With Angular/React/Vue (Vue suted me most, but it's still meh) it's halfway there but still meh.

On the .Net stack, you have battletested frameworks and libraries that have been around for ages, on both, hobbyist apps to full blown enterprise solutions. At some point I was working on a desktop app that would run on a 5*6 monitor array (highway control room software)... 30 windows open in parallel from one app, everything in sync, everything just working 24/7. And now, we'll cover Android/iOS and Windows desktop, with one codebase, and it's not just a simple CRUD app. We're connecting with RFID readers, using cameras, geo service etc... I can't imagine pulling this off, in the timeframe we did, and the amount of devs working on it, with any other stack.

Yes, there's no Linux support, but the way MAUI is laid out, it shouldn't be too hard to get that going. Just look at who and how contributed the Tizen backend. I'm sure the folks at MS will welcome you with open arms if you want to contribute some effort into making Linux happen.

isodev2• 4 years ago

Web frontend isn't even close to what any of those mentioned above are right now. Layouting stuff on the web is a nightmare.

One with more experience with web dev can easily submit the exact opposite comment - web layout and tooling are light years ahead of whatever most recent .NET endeavor.

The web is also already cross-platform, where every platform looks and feels native to itself. This announcement doesn't show off a single native macOS or iOS component. Seeing it's inspired/supported by Xamarin, APIs for look & feel are minimal unless you opt for a platform-specific implementation anyway (e.g., the "common" animations API is a fraction of what one requires for a good experience on iOS).

I'm sure MAUI will be famous in enterprise apps where the latest productivity tool needs to be put together quickly and inflicted on employees for years to come (cough* Teams, Office...).

pleb_nz• 4 years ago

I do web dev and haven't done much desktop dev in years.

But a few months back I got to play with WPF and it was an absolute joy and breeze compared to web dev IMO.

g0gzs2• 4 years ago

I'd say I'm equally fluent in both because I put heaps of effort into my web dev skills so I could charge the same hourly rate and deliver the same quality I deliver for Desktop/Mobile. I adhere to certain standards when I put my name behind something I deliver to a client.

The amount of "oh yeah, it seems hacky but that's the best practice" on web is mindboggling. Every time I had to use HTML/CSS/JS hacks to achieve something rather simple in terms of laying out components on the screen, I wanted to quit working on the project.

The amount of work you have to put into web frontend to get it pixel perfect and according to the design, is roughly 40-50% more than achieving the same thing on let's say WPF.

Take it however you want, but what MS achieves in dev experience on their UI stacks is quite admirable. The fact that those stacks don't survive long is a another pair of shoes.

Welcome to .NET Multi-Platform App UI

Related Stories