Re:Major upgrades to Xamarin’s platform: Async is here
by ghuntley on Wednesday July 24, 2013 @09:45PM
(#6100440)
disclaimer: using Xamarin, using MvvmCross and went to Evolve 2013.
- Write your core business logic API once (in a Portable Class Library) using the ModelView ViewModel pattern.
- Design native user interfaces for iOS, Android, Mac, Windows Phone 7.x, Windows Phone 8.x, Windows Store (RT and Desktop) and Windows WPF.
- Bind your user interfaces against the core business logic.
Multiple platforms, native user interface designed for each platform, sharing one core business library, maximum code reuse (90%+!), using either C# or F# with async/await/linq/lambdas/anonymous types, etc.
You can use Visual Studio or MonoDevelop.
Rewriting your business logic multiple times over in different languages to target multiple platforms does not make sense. I'm curious why would anyone not use Xamarin?
- Write your core business logic API once (in a Portable Class Library) using the ModelView ViewModel pattern.
- Design native user interfaces for iOS, Android, Mac, Windows Phone 7.x, Windows Phone 8.x, Windows Store (RT and Desktop) and Windows WPF.
- Bind your user interfaces against the core business logic.
Multiple platforms, native user interface designed for each platform, sharing one core business library, maximum code reuse (90%+!), using either C# or F# with async/await/linq/lambdas/anonymous types, etc.
You can use Visual Studio or MonoDevelop.
Rewriting your business logic multiple times over in different languages to target multiple platforms does not make sense. I'm curious why would anyone not use Xamarin?
Evolve 2013 Videos: http://xamarin.com/evolve/2013
Recommended ModelView ViewModel Frameworks: https://github.com/slodge/MvvmCross or http://www.reactiveui.net/