Thanks for the detailed response! That helps clarify things quite a bit.
And I'm sorry that the post was written with a bit too much emphasis on Infinite Red and the recent blog posts. I don't hit your blog sites daily, and seeing multiple R-N posts, well, let's just say I've had several people/potential clients express concerns along the lines of "why RubyMotion instead of Swift or Java or, even better, React-Native?" Started to feel like an approaching iceberg
I've got good answers to the Swift questions, don't much care about Android/Java, and remain skeptical about cross-platform solutions. But I was sensing a trend. And I really want RubyMotion, and Ruby at large, to succeed and thrive.
I share your frustrations and concerns about RM on Android. In all honesty, I'm not sure I'd mind all that much of they dropped the Android project and focused on doing "just" Apple's product lines. That's where their strength lies, that's where the majority of their customer base lies, and they seem to attract a lot of grief from folks who expect RM to be fully cross-platform. That is, cross platform in the sense of 'write once, deploy on iOS and Android'. We've had genuine cross-platform coding systems in the past (e.g. my beloved Smalltalk) but it's a problematic space once you get to the GUI.
Lots more attention to Apple Watch and Apple TV OS could only help. If resources are being used on Android rather than those targets I, for one, would suggest that HipByte reconsider. If nothing else, those are easier targets than 'write once/deploy anywhere'. And 'write one and a half times, deploy anywhere' just isn't a marketing winner, imnsho.
I think it would be helpful for the community to have a discussion about the pros and cons of RubyMotion versus React-Native, and hope this launches one. I also think you've done a pretty splendid job of laying out the issues and some of the reasonable answers, especially in a business perspective.
Who else wants to weigh in?