I am developing a project for a client that needs to be on Android and iOS, and would otherwise be a Cordova project with a significant amount of native code in a plugin for each platform.
I love the concept of RubyMotion and have invested many hours in trying it out on Android. I don't have a suitable iOS device to test with longterm (I need the M7). As a long time Rails developer, I love the concept of one language (my favorite) on the server and both clients.
Also both mobile clients being native, shared code, and without the complexity of Cordova plugins etc. is a massive point in RubyMotion's favour, and I really hope it gets there eventually, but I think I'm going to have to learn Java and maybe Objective C or Swift for this. I'm not sure about using RubyMotion for iOS only.
RubyMotion claims :
a) a REPL like irb : but you have to use "pro" and print-something-variables. You can't seem to just eval code (even in the REPL) which is half the benefit - to test code on the fly.
c) RubyMine IDE support : but not Intellij IDEA which I use for everything, and no debugging on Android
d) no static compile to a library on Android - which would enable creation of Cordova plugins in RubyMotion
e) I don't know what roadblocks I'll hit down the road either - this recent experience hasn't given me much confidence
So for coding I'm stuck with write-compile-install with logging and an almost useless REPL (is it worth learning gdb? Will it get me anywhere near irb?)
I think I'm going to try writing a native Android version, and hope I can convert to RubyMotion later to do the iOS version.
I just want to emphasis that being able to write the backend and both *native* mobile clients in Ruby is an AWESOME proposition, for Ruby developers and otherwise. Maybe I'm wrong, but I don't think it's there yet on Android, and the pace since the Android prerelease doesn't convince me I can use it right now while being paid for it (I can't afford any more of my own time).