I began the project of my client with MonoCross and it was great. The change was significant, MonoCross has many of the benefits that ASP.NET MVC also has: route system, uncoupling between layers and many others. When Greg (thanks to him) named a few benefits of MVVMCross, I thought "ok, they are good, but I can reach them on my own, e.g. easy test or DI.." But I couldn't be more mistaken, the last two days I have been playing around MVVMCross (basically setting up the environment and learning the basics).
Today I tasted the power of MVVMCross. I didn't think it twice, so I started to migrate my client's project from MonoCross to MVVMCross and in a few hours I had almost half of the project migrated. It was easy for me because under the hook, MC and MVVMC are similar and I made a good separation of the concerns, so I only had to make a few changes to my code. I really think that MVVMCross should be included in Xamarin's stack, with MVVMCross under the arm the crossplatform development (and also the non-crossplatform) goes to the next level. Thank you Stuart!! Juan M Gómez @_jmgomez_ Software Engineer 2013/1/12 Greg Shackles <[email protected]> > I haven't used MonoCross, but I have been using MvvmCross so I can provide > some opinions there. > > TL;DR: shared behavior, native views, testable, extensible > > > I have really enjoyed using the framework for a variety of reasons: > > - Binding support on iOS and Android > - A lot of app behavior gets put into viewmodels and is reusable > across platforms > - Since viewmodels are platform-agnostic, I can write unit tests that > cover most of the app's behavior > - View models are shared, but views remain totally native > - You can customize how view models are presented based on your needs > (such as showing multiple at once for a tablet version) > - DI/IoC can be used > - The framework itself is very extensible, allowing for a lot of > customization if you need it > > I realize this basically ended up being more of a features list, but it > sums up the main reasons I continue to happily use the framework. Hope this > helps! > > > - Greg > > > On Fri, Jan 11, 2013 at 6:17 PM, Juan M Gómez <[email protected]>wrote: > >> Hello, >> I'm thinking about using MonoCross for my new customers monotouch app ( >> he'll probably want an android version too), I played a little with it and >> seems very nice. I'm asking if anyone used it and can tell me the >> experience. I'm also considering MVVMCross, Stuart's fork, but I think that >> this one is a bit less stable, however if you can tell me your experience I >> can make a better choice. >> >> Thank you, >> >> Juan M Gómez >> @_jmgomez_ >> Software Engineer >> >> _______________________________________________ >> MonoTouch mailing list >> [email protected] >> http://lists.ximian.com/mailman/listinfo/monotouch >> >> >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
