-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MvvmCross roadmap and plans #4467
Comments
I work on it when I have time and also when something we've found in the Apps need fixing. Plans for the near future:
In general, my idea is to have strong support of native Apps. And leaving the third party MAUIs, Unos and Avalonias as community support rather than baking it into MvvmCross. It is just too much for me to support every possible thing in the .NET ecosystem. |
For some reason I am against using VMs from anywhere but MS. And these don't exist. Having its own VMs is better IMO. |
@Cheesebaron It would be very good to have some brief instruction how to migrate existing MvvmCross.Forms project to MAUI without MvvmCross.Forms (or maybe without MvvmCross at all?) to know what is replacement for In any case, thank you very much regarding what you have already done! |
@Cheesebaron recently I played with new Fragment API (that is allowed multistack out of the box) and made a little library with multi-backstack aware Android presenter https://github.com/Paul-N/EvilGenius.MvxTabbedNavigation May be you would like to take a look. Also there's a support of native Android ViewModel hadling in my lib. |
What are the plans to support .net for IOS and .net for Android, the Xamarin successors? IOS 17 is not being released for Xamarin.ios and apps usually have to be build using latest IOS SDK around April next year. Will Mvvmcross become obsolete or will it continue to work. |
New .net platforms already supported, check out new versions of MvvmCross |
Blazor WASM support would be awesome too |
@Cheesebaron I'm interested in what you're referring to with this (long time ago I know) We use a single activity multiple fragment approach in MvvmX and have had no issues with fragment navigation support really (bar some custom presenter logic for modal stacks). What do you think it's missing from Mvvm? So you mean better support to not just do a fragment replace, or expose the fragment transaction more easily? Also - when it comes to Android navigation graph stuff - imo I wouldn't bother. My experience of using that in a few native apps has taught me..... To not use it again 🤣 Hated it. |
I was thinking of adopting the navigation graph and what it provides, but i haven't used it extensively so don't have much experience apart from some simple navigation. There is much that could be done, but too little time. |
Mvx and Xamarin.Forms combination was the best thing I had used ever, however, as Xamarin.Forms is deprecated, it would be nice to port its features to Maui as there doesn't seem to be a cross-platform UI framework supporting Mvx anymore :-( Also, it seems that some work was done for Uno Mvx, but it has been abandoned?!? |
I'm wondering what is the situation with maintains and future support of this library? Do you have any roadmap or docs showing your plans. For a long time since summer 2021 we haven't seen the new major or even minor releases. Is MvvmCross still actively developing?
The text was updated successfully, but these errors were encountered: