This seems like a viable approach in the future. I hope you are not suggesting that it is OK to send code compiled with a beta version to a client.
back
1 comments
> I hope you are not suggesting that it is OK to send code compiled with a beta version to a client.
If the client's demanding a single-codebase solution for both Android and iOS and you are better at Ruby than you are with either Java or Objective C, then it might make sense to sell the client on using the beta.
I guess it depends on the client, if he is willing to take the risk that, for e.g., his app won't be compilable with the final version of RubyMotion. You can probably convince him it is a good idea if you specify in your contract that you will offer support in the future when RubyMotion for Android is stable.
I think RubyMotion could be a good idea, even today, for someone that knows and use Ruby for his own projects.