Skip to content
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

Open
AndreyPhilippov opened this issue Sep 5, 2022 · 10 comments
Open

MvvmCross roadmap and plans #4467

AndreyPhilippov opened this issue Sep 5, 2022 · 10 comments

Comments

@AndreyPhilippov
Copy link

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?

@Cheesebaron
Copy link
Member

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:

  • Look at re-doing the startup code of MvvmCross to conform with IHost
  • Support or switch out IoC with Microsoft.Extensions.DependencyInjection
  • See if we can replace or supplement with ViewModels from the CommunityToolkit
  • Redo Presenter for Android to better support proper Fragment navigation
  • Rework Presenter code and perhaps support navigation graphs, perhaps hook into some of the native stuff

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.

@entdark
Copy link
Contributor

entdark commented Sep 5, 2022

For some reason I am against using VMs from anywhere but MS. And these don't exist. Having its own VMs is better IMO.

@AndriDev
Copy link

AndriDev commented Sep 13, 2022

@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
Setup.cs in Android/IOS
MvxFormsApplicationActivity/MvxFormsApplicationDelegate in Android/IOS
MvvmCross Plugins
MvxViewModel (ShowViewModel<>)
custom Presenter
etc.

In any case, thank you very much regarding what you have already done!

@Paul-N
Copy link

Paul-N commented Jan 2, 2023

@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.

@ggbtvs
Copy link

ggbtvs commented Jun 15, 2023

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.

@Paul-N
Copy link

Paul-N commented Jun 16, 2023

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

@amirvenus
Copy link

Blazor WASM support would be awesome too

@IainS1986
Copy link

Redo Presenter for Android to better support proper Fragment navigation

@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.

@Cheesebaron
Copy link
Member

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.
These were just ideas of what could be done, so more investigation work would need to be done.

There is much that could be done, but too little time.

@amirvenus
Copy link

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?!?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

8 participants