This is where patterns like MVVM come in. You model, view and viewmodel don't change (or change very little). But your view (which sits above the viewmodel) changes a lot.
It's not an easy thing to design, but it's better than c# + java + obj-c On Wed, Aug 10, 2011 at 13:39, kbudris <[email protected]> wrote: > I've only worked with MonoTouch so far... haven't yet needed to work on > Microsoft or Android devices. Just how portable is a MonoTouch app to > Android? I can see where I might be able to reuse the data model, but the > entire presentation layer seems so Apple-specific. Wouldn't the entire UI > need to be scrapped and rewritten for Android? > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Performance-cost-of-MonoTouch-vs-Objective-C-tp3715348p3732787.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
