The thing I found about RubyMotion is that the default APIs are just straight mappings to the Objective-C APIs, which eliminates most of the advantages the Ruby

The thing I found about RubyMotion is that the default APIs are just straight mappings to the Objective-C APIs, which eliminates most of the advantages the Ruby language could offer. Your code ends up being an essentially line-by-line copy of what you would write in Objective-C. I never dove into any of the (meta-)frameworks designed exclusively for RubyMotion, but I do believe there could be some nice advantages to using it there. As much as I do appreciate the Cocoa Touch design, there is always room for improvement.