Is it already foreseeable when MAUI can be used professionally to develop apps? #21277
-
DescriptionI want a working MAUI development environment in which I can develop software professionally.
This is like software development in the 90s! Steps to ReproduceUse MAUI and be frustrated! Link to public reproduction project repositoryNo response Version with bug8.0.7 SR2 Is this a regression from previous behavior?Not sure, did not test other versions Last version that worked well8.0.7 SR2 Affected platformsWindows Affected platform versionsNo response Did you find any workaround?NO Relevant log outputNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 10 replies
-
I don't think this is particularly productive as an issue, let alone a discussion.
I think this is circumstantial. Likewise in WPF, and co, Binding errors/warnings can exist because of ordering of initialisation, race conditions or merely to let you know something is non optimal, i.e. conversions from null etc. Historically these have always been "maybe there's a problem". Depends if they're internal or not.
Not really sure what to do with this one. There are third party component partners that have tables, as well as being able to build one in Blazor and use in Hybrid? I suspect you're after a better data grid/table solution? They're usually never a good answer on mobile layouts.
I think again this is circumstantial. Maybe share a demo and others could look at it?
Not sure I've personally seen pointless error messages, this also looks like a warning to me.
Depending on what you're using, you're using a model that was trained in a time where Xamarin was the goto. MAUI is still relatively new. Not much the MAUI team can do here.
Quite vague. File issues and help the product forward. |
Beta Was this translation helpful? Give feedback.
-
@DominikErnst for errors and warnings as you've described please file VS feedback issues. To improve your experience with GPT, add more context to your prompt to help guide it. That will improve with time, and as Copilot itself is improved (if you're using Copilot). |
Beta Was this translation helpful? Give feedback.
-
Seems like this was moved from #21272 but somehow ended up in the Announcements category, where it probably doesn't belong (seems quite exposed there, which is why I ended up here in the first place; this showed up on my github.com homepage as an announcement). /cc @PureWeen as you originally converted the issue to a discussion if I get the GitHub UI right... |
Beta Was this translation helpful? Give feedback.
-
Have you tried increasing the TabbedPage.OffscreenPageLimit? |
Beta Was this translation helpful? Give feedback.
-
@davidortinau - the original question was about when MAUI can be used professionally. Well, I am not saying it is not possible to use it professionally. But, what really is a pain sometimes is that there are still a lot of Bugs in layouts, But, my problem really is, that after writing these issues nobody seems to care about them anymore for very long time. I still have unsolved issues from September and others have some of them even longer. When I look at the fixes and checkins on this project on a daily basis, my impression is that the majority of checkins appear minor and far away from the bugs that are reported daily. To me this is a big problem regrading the subject „can we work professionally“. The basic controls and mechanisms should be clean so that we can work professionally. And if issues come up it should be possible to get it fixed in an acceptable time frame, otherwise people that doing it professionally are stuck. And if you have to pay people it is even worse and the money can kill everything. I was lucky that I could find workarounds for things that did not work as intended. But it took me hours to days. And I could have invested this time better to get my App done 😉 I know this sounds like a big complaint. Yes a bit, but it is not meant in a nasty way. I just wanted to ask if it wasn’t possible to hire more people for this project to fix Bugs sooner or at all? I wrote Bugs beginning of September and now it is April. Working professionally from a developer perspective is the other way around. How would a company finish their products when they are waiting so long for stuff they can’t find a workaround for? Then I also do not get it why a solution is so close and someone already provided a Pull request but it doesn’t find it’s way into the code and why there is no solution available My biggest wish for this project really is that the open Issues are scanned for things that relate to "Standard Controls", Layouts or Controls like |
Beta Was this translation helpful? Give feedback.
I work with it professionally.
Yes, it involves a lot of frustration, but it's been improving a lot over the past year. The most annoying issues by now involve the tooling and not the quality of MAUI.
I still think that MAUI has a great concept and I love the new possibilities it brings.
I'm currently migrating some XF apps to MAUI and they work much smoother and faster. I can even use less third-party controls now. And every professional app in one way or another relies on workarounds, there's no perfect framework.
It's in flux, there are major improvements and the community is very actively supporting the dev team in various ways. I want MAUI to succeed so I participate instead of only …