https://www.ibm.com/developerworks/community/blogs/mobileblo...
Weird.
Have you considered Ruby? With Ruboto for Android and RubyMotion for iOS, I'd think you could get a pretty good single-codebase solution. I ask because as a Ruby dev who may one day branch out, I'd like to know what I'd be getting myself into, and it sounds like you might have gone down that road.
http://blog.rubymotion.com/post/97668474211/announcing-the-p...
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 think RubyMotion could be a good idea, even today, for someone that knows and use Ruby for his own projects.
Except this is not possible, as you have to recode the UI for each device anyway.
So just go C++, or any other language with compilers that can target C, and do as little as possible in the UI part.
Companies like Dropbox are following this approach.
All that said, I would normally advise a client not only to have native code, but also large amounts of native design for their main platform targets. Lots of Android apps suffer from port-itis. Transliterating an iOS implementation inevitably makes for a lackluster Android app that underutilizes Android modularity features among other things Android does well.
Doing what Xamarin does is VERY hard and Xamarin hasn't had big-time funding until recently. And they can't stop and just fix bugs, like the article author would like. Xamarin is on the treadmill and has to keep up with two platforms that are in competition with each other. The only good news in that is that they will probably converge in terms of capabilities. But, damn, I wouldn't want that job.
3rd party dev tools are a thankless and usually VC-less pursuit. The investors are probably hoping for an exit in the form of Satya Nadella taking C# and VS cross-platform and using it for Microsoft's own apps.