Hey Bill, thanks for posting the question! You’re right, lately we’ve been posting a lot about React Native. So, I thought I’d give a little context to where we’re at with regard to RubyMotion.
I know we’ve been a little quiet lately on the forum, open source, and Motioneers Slack channel. It’s not because we’re not doing RubyMotion anymore -- quite the contrary. We have several RubyMotion projects in progress right now. It’s still in our primary iOS and OSX (and Apple TV!) stacks, and we don’t intend on abandoning it anytime soon.
But to be frank, RubyMotion Android has been a real pain point for us. We’d been working on BluePotion for months leading up to #inspect2015, and when we demonstrated it, it still had a lot of sharp edges, which Darin Wilson was pretty open about in his talk. The two significant RubyMotion Android projects we’ve done ended up costing us a lot in terms of hours burned on avoidable bugs and issues.
React Native has been on our radar for a while, and when the Android version was released in September, it was almost perfect timing for us. We had two new iOS + Android projects that were starting in October (and if you don’t know, ClearSight and InfiniteRed merged to form the new Infinite Red right around then). So, we kicked off the two projects in React Native.
We still love RubyMotion iOS/OSX/tvoOS, and when Android is fully stable and performant, we may put some more attention on BluePotion. We still support RedPotion and its constituent pieces. But for pragmatic reasons we have diversified our tech stack.
I hope this clears things up for you!
Founder and COO, Infinite Red