Yes. iOS. Everything but UI was C#/Xamarin. Biggest pain was ramping on iOS and not realizing just how awful Storyboard was and how many was the Xcode designer

Yes. iOS. Everything but UI was C#/Xamarin. Biggest pain was ramping on iOS and not realizing just how awful Storyboard was and how many was the Xcode designer wanted to screw me. The integration between the two using Xamarin Studio on the mac felt slightly clunky at times. Tweak UI, hook up event handlers, go back to Xamarin... watch it pull those changes across. If it failed, and it did at times, you could end up repeating changes. Xamarin Studio is not Visual Studio. Better than Xcode, but it's not nearly the tool VS is. Final app is a native experience nearly on par, performance-wise, with objective-c stuff. Most perf issues I hit also had more to do with working through iOS patterns & practices (e.g. long table views/lists with custom cells). The cons are usually friction and requirements to understand more than a single tool/language. You will need to bring up multiple games at once. There is a 1:1 mapping between iOS SDK and library access in the Xamarin API. I also did the kata thing and made simple apps to deploy across platforms just because I could. That was fun.