Ask HN: frameworks vs native apps

This is the opposite of how you should approach the problem in my mind. Why don't you want to use the framework? There must be some reason.

Good reasons not to use it:<p>* you are only interested in developing for one platform--ios.<p>* you have obj c and any other language talent in house, but don't have c# talent<p>* you need to use tons of custom native libraries that the framework doesn't have bindings for<p>* you want to avoid vendor lockin

It is going to allow you to use slightly more familiar syntax<p>You're still going to have to learn and use all the libraries in your iPhone app in ObjC<p>If you have crushing large amounts of business logic, you might see gains

List of limitations.<p><a href="http://docs.xamarin.com/ios/about/limitations" rel="nofollow">http://docs.xamarin.com/ios/about/limitations</a>

well, monotouch is a really nice framework. but, speaking about downsides, you'll need to spend time on writing custom objc bindings if you would want to use something that is not bound yet (e.g. custom library). and that can take quite some time. other than that - it's quite the same as native (may be a tiny-tiny bit slower)

Actually if you cannot find "good reasons to not use it" by yourself, usually it is better to "use it"

MonoTouch is what you're referring to, and it has its pros and cons. Pros are, one app can be published on multiple platforms with little to no change.<p>Minuses, it's expensive and you have to wait for access to new features until they've been released by Xamarin.<p>Writing an app for iPhone using this is easily 2x faster than learning and then writing it in Objective C. It does generate a "native" app, for what it's worth.<p>Sounds like you just need to get past your dislike of C#, and your boss sounds like a pretty smart person ;-)<p>(disclosure : I'm not his boss)