Alright, I’ll bite.
I found that when jumping headfirst into building for iOS the challenge was getting familiar with the cocoa touch API and the “idea” of MVC in the context of a true GUI application.
With regards to the MVC thing - If you’ve been programming exclusively on the web for a while the request/response model can pretty much get thrown out the window. It doesn’t take that long to wrap your head around it but when you’re dealing with figuring out the api, the toolchain, the open source landscape - it’s a lot.
Apple’s API docs are good but it’s big. One thing I noticed, also, was that while the docs are GOOD there aren’t a whole lot of examples in the docs themselves. You’re left to google and search through SO - which helps.You should thank @mark for a lot of that good stuff.
So where would I come down on the answer for this?
If you’re in a rush and under a deadline - go with rubymotion.
If you have time and a support system (coworkers, consultants, etc) - go with Obj C.
I’m, personally, in a tight development window so I went with Rubymotion and I’ve been happy with it.
One thing @gfontenot and @tonyd256 neglected to bring up is Xcode. Guys how awesome is Xcode, right?!?
Last thought - I don’t think there’s a wrong answer here. Just pick one and go with it and be happy with it.