a subset of the .Net framework • Cannot use compiler directives • Not all PCL’s are created the same • Shared Projects • No output assembly • Can be branched based on compiler directives • Refactorings for non- compiler directives do not update code Code Sharing
also morphs some of the native language constructs into their .Net equivalents, it isn’t just a wrapper. E.g. NSString simply becomes string • The official designer tools (Xcode / Ellipse) Xamarin Helps to Hide…
development with Xamarin? Particularly around ReactiveUI. The reason I'm excited about Xamarin is that it's a cross-platform solution that's actually *better* than the original platforms. C# is one of the best general- purpose programming languages, and with Xamarin I can write code for platforms that people use (iOS and Android) I'm excited about ReactiveUI because it's a foray into fundamentally changing the way that people write the backing code for user interfaces, in a way that takes extremely difficult state-management / race condition'y problems, and turns them into succinct, deterministic, elegant code. RxUI makes it reasonable to do otherwise prohibitively difficult things in user interfaces. The fact that it's cross-platform is really just a bonus - my goal for Xamarin and RxUI is to be the best way to write client software, flat-out.
/ Android applications with .Net & code sharing, what excites you the most about the Xamarin product going forward? I'm mostly excited about the platform that can be built on *top* of Xamarin products - taking all the great ideas from platform-specific libraries like Picasso and Volley, and creating cross-platform versions that are both better to use (because of C# the language), as well as making it easy to write beautiful applications that run everywhere.
night in the dusty recesses of their minds wake in the day to find that it was vanity: but the dreamers of the day are dangerous men, for they may act their dreams with open eyes, to make it possible.’ T.E. Lawrence