You're going to have to learn Swift, and probably at least the mechanics of Obj-C anyway. I've worked with PhoneGap, RubyMotion, and even a bit of Ruboto when i

You're going to have to learn Swift, and probably at least the mechanics of Obj-C anyway. I've worked with PhoneGap, RubyMotion, and even a bit of Ruboto when it first came out. All of the documentation is written for Swift, and the examples are, or were, in Obj-C (though I haven't seen it in a while so I assume they converted all that to Swift by now?). It's not a question of "which one should I learn"? You'll have to learn Swift, or at least a little bit of it, eventually to stay up-to-date with the API docs. RubyMotion can certainly be an easier (and maybe more stable?) way to express what you're doing, but you're going to have to learn the mechanics of the base system in order to work with it, eventually. So, as a Rubyist who love's Laurent's work even back to MacRuby, and mostly programs in Ruby these days, I say just learn Swift. From a pure language-appreciation perspective, as opposed to the practical perspective illustrated above, it's in Apple's best interest to make Swift easy to work with for app developers, because that's Swift's target market. Ruby, on the other hand, does not have that same guarantee.