RubyMotion Moving Forward Under New Leadership
rubymotion.com
rubymotion.com
I think react-native has largely filled the niche that was there for rubymotion to fill and with the momentum of facebook and javascript behind it the days of new people coming to rubymotion are largely behind it.
It was a great idea and a great product/tool in its time, but it was outflanked by additional resources and circumstances.
Ionic 1 seemed pretty straight forward to me and I haven't tried React Native.
redpotion.org
There are a few other libraries/frameworks from the rubymotion project itself, called motionflow iirc, that seemed like they were the way of the future when I checked out status a few months ago. However they were not finished at the time.
Swift looks like a nice language from the few hours I have spent playing with it, but I hope that RubyMotion as a company stays viable because for someone like me, who just dabbles in iOS and macOS development, RubyMotion is easier.
The iOS gems made getting an app out the door easy if you were already a Ruby developer. Android, not so much. The support for Android was still fresh. The APIs to interact with Android were there, but not very many gems for Android + RubyMotion at the time. However, there hasn't seemed to be much progress with RubyMotion + Android since then.
React Native was a good alternative and appeared to pick up more steam. Likely because of the rise of React. Since this targeted iOS and Android better, it was more exciting to put effort there.
As a Ruby developer, I'm excited to see what's to come! I'd love to give RubyMotion another chance.
http://blog.motioninmotion.tv/why-swift-will-never-replace-r...
https://katanacode.com/blog/posts/12-a-review-of-rubymotion-...
I remember a few years back when Hypercritical revisited Copland 2010. RubyMotion looked like potential future, but Siracusa didn't believe in bridges.