Hey, Xamarin CEO here, thanks for your feedback. A couple comments/questions on the issues you raised. 1) We aren't aware of any debugger issues like this. Is

Hey, Xamarin CEO here, thanks for your feedback. A couple comments/questions on the issues you raised. 1) We aren't aware of any debugger issues like this. Is it possible you were debugging optimized code which had the local variables optimized away? Similarly, when an uncaught exception is thrown, it comes with a stack trace with line numbers. Were you not getting these? 2) Xamarin does map the entire set of iOS and Android APIs into C#, so yes it is a "wrapper," but you should NOT be limited in what native features you can use. We literally cover almost 100% of the entire set of native APIs. What limitations were you running into? 3) We have a ton of docs at http://developer.xamarin.com http://developer.xamarin.com including nearly 300 sample apps and a lot of very detailed guides: http://developer.xamarin.com/guides/ http://developer.xamarin.com/guides/ Which part of the docs did you find inadequate? 4) We do include XAML intellisense in Xamarin Studio. To get it in Visual Studio you have to install an extension: http://www.cazzulino.com/mobileessentials.html http://www.cazzulino.com/mobileessentials.html This will be included by default in a future version of Xamarin. I'm sorry about the trouble you had, and I'd like to get to the bottom of those issues. Please feel free to contact me at nat@xamarin.com.