We used to use monotouch a lot, but as soon as we tried to use any third party sdk it was a huge mess. All of the ones supplied by xamarin never quite worked/w

We used to use monotouch a lot, but as soon as we tried to use any third party sdk it was a huge mess. All of the ones supplied by xamarin never quite worked/were out of date and threw a bunch of weird errors. Of course there is a way to write your own bindings, but the those threw a bunch of undecipherable error messages as well and never really worked either. The main problem was that there were way too many possible sources of the errors to try and just diagnose the problem and the error messages themselves were useless. So basically xamarin was great as long as you didn't need to use a third party sdk and there is 0 chance that down the road you might need to use a third party sdk. That was really the deal breaker for us, that we were severely limiting our future capabilities on any app we made with monotouch. Also it is often difficult to pull in third party c# libraries because monotouch uses weird versions of all the main .net references. But this was not the main problem. In the end it is just much easier to bite the bullet and use obj C.