[tfranco]

Amir, thanks for following up. Like I said in the article, I've used RubyMotion in production in the past. We were one of the early adopters and launched at least half a dozens apps in it. We payed for all our licenses. I love the product and this was money very well spent. It allowed us to use the same language (Ruby) in a larger portion of the projects. This was particularly important when some of our clients were small startups with an existing Rails app, and it was important for them to keep the same language for the mobile app.

I just think the support for Android should have happened a lot sooner. But of course this is easier said than done.

Moving forward to React Native is part of the same approach. It's important for us to use a technology that delivers fast in multiple channels and has a great chance of still being relevant in the next 10 to 20 years. And for me, these are the strongest points on Javascript.

And you're correct, React Native is not truly native, but it does the job pretty well without major impacts on usability. RubyMotion is truly native and very well designed IMHO.

Best of luck for the future.

[amirrajan]

I totally understand the need for Android support back then (and to your point should have happened sooner).

With regards to relevancy, RubyMotion is built on top of LLVM. With regards to Ruby the language itself, it's been around for decades and won't be going anywhere (granted the same can be said for JavaScript).

I'm waiting to see how web assembly will shake things up.

Best of luck to you man (I genuinely mean that). And if you ever decide to come back to RM, I'll be here to help :-)

[tfranco]

Thanks. Same here. I truly respect the work that has been done on RubyMotion. Like I said in my post, brilliant people there.