4 ms·
If you're going to make a shared backend between Android, iOS, or other platforms Xamarin supports, I highly suggest using MvvmCross to guide the structure of y
by hart_russell 10y ago
If you're going to make a shared backend between Android, iOS, or other platforms Xamarin supports, I highly suggest using MvvmCross to guide the structure of your project. I've worked on a project with a custom backend and it was a monster of a codebase that I never was able to fully understand. However, if it's mostly just UI and little backend, do your own backend, because MvvmCross would introduce unneeded overhead.
Let me know if you have any other questions.
- cptskippy 10y agoWe maintain a large app using MVVMCross, it was originally using Forms in the PoC but had to be rewritten because of a number of issues. Off the top of my head I remember there were a lot of UI issues, binding to native modules was next to impossible in some cases, and it was buggy and unstable for complex interaction.