Description
Let me start total admiration for the team and what they achieve considering how small they are as a team..
@davidortinau @maddymontaquila
Unfortunately you are the face of Maui and I bet you have your hands tied too but the state of Maui continue to be a problem
We are trying very very hard to convert applications written in Xamarin to MAUI but we face a daily struggle to get things working.
We are stuffing our apps with workarounds everywhere and something that should be just a port has quickly turned into a massive scope creep because simple things just dont work on Maui.. I know you know this but we need some transparency and some quick action from yourself - We love the initiative that @PureWeen took with his nuget - it cleared quite a few bugs for us.. why dont you do the same for collectionview??
Basic things that should just work and they dont
- CollectionView - resize - EmptyView and a miriad of bugs but EmptyView not working is a pain, and involves a big workaround for us with crappy code to hide /displays screens.
- Gesture recognizers - Common !! we had to go on discovery tour to find out which control they work on - they dont work on collectionview and frame etc...
- Line breaks in entry - here we go again writing handlers to fix this.
- Release mode has some nasties - I.E Visual state on iOS does not work
- Image -clipping with borders do not work
- Keyboard issues on iOS covering the entry.
- We have no official UI Testing framework
The list goes on - all of these items have already been raised as bugs but never fixed - we need the basic stuff working!!!!
We seem to get the dreaded "Moved to the backlog" we all have one of those and wherever I worked means - "It will never be fixed!!"
I am trying to be constructive here , but unless you start dogfooding - writing apps that go live - you will never hit a miriad of issues that we encounter when we are writing real apps...
I know you are forced to move to the .net 8 bandwagon , but here we are in a very much broken state till Nov 2023 with the hope that magically it will all start working...
We totally understand that any framework has bugs but it defeats any logic in trying to even support windows when you can barely support iOS and Android.
@maddymontaquila HotReload - we desperatly need this working reliably , its a massive hit and miss -
Ask one of your developers to build some apps - with 10 -20 screens - popups - bottomsheet- collectionViews etc and then try to use hot reload in both ios and android - than you will know what we are talking about!
I hope I get some response because I am struggling to justify to managment on why its taking me too long to port the app to Maui!!
Finally -Why cant you give us an interim nuget with fixes like @PureWeen does ? that would help the community enormosly!
Its not ideal but its a solution that will give us a chance to move on into the Maui world..
thats all
Steps to Reproduce
Write any decent size app and you will see all the issue we daily encounter
Link to public reproduction project repository
you could port smart hotels to maui
Version with bug
6.0.312
Last version that worked well
6.0.312
Affected platforms
iOS, Android
Affected platform versions
VS 2022 any version
Did you find any workaround?
We are making our app so brittle with all these plasters here and there!
Relevant log output
No response
Description
Let me start total admiration for the team and what they achieve considering how small they are as a team..
@davidortinau @maddymontaquila
Unfortunately you are the face of Maui and I bet you have your hands tied too but the state of Maui continue to be a problem
We are trying very very hard to convert applications written in Xamarin to MAUI but we face a daily struggle to get things working.
We are stuffing our apps with workarounds everywhere and something that should be just a port has quickly turned into a massive scope creep because simple things just dont work on Maui.. I know you know this but we need some transparency and some quick action from yourself - We love the initiative that @PureWeen took with his nuget - it cleared quite a few bugs for us.. why dont you do the same for collectionview??
Basic things that should just work and they dont
The list goes on - all of these items have already been raised as bugs but never fixed - we need the basic stuff working!!!!
We seem to get the dreaded "Moved to the backlog" we all have one of those and wherever I worked means - "It will never be fixed!!"
I am trying to be constructive here , but unless you start dogfooding - writing apps that go live - you will never hit a miriad of issues that we encounter when we are writing real apps...
I know you are forced to move to the .net 8 bandwagon , but here we are in a very much broken state till Nov 2023 with the hope that magically it will all start working...
We totally understand that any framework has bugs but it defeats any logic in trying to even support windows when you can barely support iOS and Android.
@maddymontaquila HotReload - we desperatly need this working reliably , its a massive hit and miss -
Ask one of your developers to build some apps - with 10 -20 screens - popups - bottomsheet- collectionViews etc and then try to use hot reload in both ios and android - than you will know what we are talking about!
I hope I get some response because I am struggling to justify to managment on why its taking me too long to port the app to Maui!!
Finally -Why cant you give us an interim nuget with fixes like @PureWeen does ? that would help the community enormosly!
Its not ideal but its a solution that will give us a chance to move on into the Maui world..
thats all
Steps to Reproduce
Write any decent size app and you will see all the issue we daily encounter
Link to public reproduction project repository
you could port smart hotels to maui
Version with bug
6.0.312
Last version that worked well
6.0.312
Affected platforms
iOS, Android
Affected platform versions
VS 2022 any version
Did you find any workaround?
We are making our app so brittle with all these plasters here and there!
Relevant log output
No response