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
