I don't know if it has since improved, but .NET MAUI was really, really rough when I created a mobile app for my employer last year. I'm talking basic things - changing basic colors on the toolbar (1), putting non-text content inside a button (2), basic trigger behavior (3), to list a few. Not to mention that .NET UI has been years behind on hot-reload and developer tooling. Additionally, It was a fight to keep our app performant. The XAML compiler is a step in the right direction, but we had relatively simple views (in the dozens of components) absolutely tanking our FPS. I know there is probably some of my skill issue in there, but when I find basic things taking hours to optimize that I wouldn't even think about in React, I start to wonder about the framework. I spent a lot of time creating PRs on .NET MAUI but their team appears quite small and overloaded. I wish them the best - they're some talented folks, but I don't envy their job.
I can't help but think of Joel Spolsky's Things You Should Never Do (5) - the transition from Xamarin to .NET MAUI feels like a very similar mistake to Netscape. All of the battle tested Xamarin code, documentation, community examples, packages, etc. is now dead and has to be converted over to .NET MAUI.
On top of that, XAML just doesn't do it for me - having to deal with code-behind, MVVM view models, custom converters, and the actual XAML files themselves is insane for what is usually just a a single file in JS. The fact that you need to write a "InvertedBoolConverter" (4) just to flip a boolean is the most Microsoft thing ever. MAUI feels like it's designed just to keep a large development team busy. I'm not joking, we have a 42 line file that's only purpose is to flip booleans for XAML views.
We're a C# shop so it was nice to share our common C# with our desktop application, but I don't think it was worth it in the end. Sure JS has its problems, but I'll take those problems any day over MAUI.
I hope Avalonia can fix .NET MAUI - it'd be a massive kudos to them if they can smooth it over, but I can't say I'd willingly rely on this project long term.
Well, I guess Avalonia can solve 4 at least as you can negate a binding[1]. Good news for me as I recently started an Avalonia project, and thought you did still need an InvertedBoolConverter.
I'm working on boiling the ocean - we're building a new CRM to compete with some of the big players. I tried very hard to avoid doing this, but I've helped enough business owner friends set up CRMs to realize there's MUCH to be desired. My goal is to create a CRM that people rave about - something that is very rare. Pretty much everyone I help views CRMs as a necessary evil. Our bold challenge is - can we make a CRM that is delightful to use?
Of course we have to slap "AI" on it in this market, but we plan on adding AI features that are actually thoughtful and not just a glorified chatbot.
Sounds interesting! As someone who works in Revenue Operations the CRM space is ripe for disruption, especially around using CRM data to help sales teams explore the data.
I vibecoded a POC of what something I think would work (around the latter part around exploring the data). Need to complete it and start testing it.
Thanks! I totally agree. It starts with getting the basics right. I think this is where most CRMs get it wrong - getting users to correctly enter and maintain clean data is a challenge. We're trying to build smarter schemas for contacts, quotes, sales, etc. but we're also making a really intuitive UI for easily updating information. Further still, we're trying to automatically fill in data for the customer. Many fields can be automatically inferred based on the context of a deal.
Once we get this right, I think the next step is exactly what you said, building really good tools to explore the data. Making it easy for non-technical users to run machine learning on their data to make business decisions or see cool visualizations. We realize that so many of our customers want to know this stuff and have no way of getting at it! We've got a lot of ideas for both visualizing and analyzing the data. I think there's a ton of potential for cool things here. Heatmaps, spiderwebs, interactive charts, etc. Stuff that brings the data to life. One of the common asks from some of our early customers is a heatmap of the world to visualize their sales/reach and see changes over time. Visualizing progress per sales region, etc. I think sales especially has a lot of opportunities for better lead generation and qualification as well.
i'm currently unemployed but i have experience as a CSM and account manager for multiple companies (all have used Salesforce) if you ever want feedback or bounce ideas.
This would be awesome, we're in hardcore MVP build mode right now - when we get closer to launch I'll hit you up.
I'm a little delusional, but I think there's ground to steal back from Salesforce. Most folks I talk to hate how complicated Salesforce is (one even calls it Salesfarce). I've heard a story or two about smaller companies trying to adopt it and wasting a hundred thousand or two implementing Salesforce only to have it never get used. On top of that, you need to train your employees to use Salesforce effectively.
The key is simplicity, building a CRM that anyone can instantly understand just by looking at it. This is insanely hard but I think we'll pull it off. I'll show you more what I mean when I reach out. Thanks!
I can't help but think of Joel Spolsky's Things You Should Never Do (5) - the transition from Xamarin to .NET MAUI feels like a very similar mistake to Netscape. All of the battle tested Xamarin code, documentation, community examples, packages, etc. is now dead and has to be converted over to .NET MAUI.
On top of that, XAML just doesn't do it for me - having to deal with code-behind, MVVM view models, custom converters, and the actual XAML files themselves is insane for what is usually just a a single file in JS. The fact that you need to write a "InvertedBoolConverter" (4) just to flip a boolean is the most Microsoft thing ever. MAUI feels like it's designed just to keep a large development team busy. I'm not joking, we have a 42 line file that's only purpose is to flip booleans for XAML views.
We're a C# shop so it was nice to share our common C# with our desktop application, but I don't think it was worth it in the end. Sure JS has its problems, but I'll take those problems any day over MAUI.
I hope Avalonia can fix .NET MAUI - it'd be a massive kudos to them if they can smooth it over, but I can't say I'd willingly rely on this project long term.
1 - https://github.com/dotnet/maui/pull/15612 2 - https://github.com/dotnet/maui/issues/8191 3 - https://github.com/dotnet/maui/pull/15655 4 - https://learn.microsoft.com/en-us/dotnet/communitytoolkit/ma... 5 - https://www.joelonsoftware.com/2000/04/06/things-you-should-... https://github.com/dotnet/maui/pull/16965