Hi everyone!
Anyone has experience with Rubymotion? would be better than React Native?
We need develop one app in Android and iOS in our job so…we started with React Native but…i dont know…we stuck every time and some modules where we try to use dont work properly or have a lot of bugs…please, OPIONIONS ABOUT BOTH ARE WELCOME
If you have a lot of time, you can even endlessly try to deal with this. For my part, I can only say that it is more convenient for each developer to work with what he is better versed in. There can be no clear and unambiguous answer here. For example, at Lomray they are developing for ReactNative, of course they will need more time to figure out Ruby
I released 2 different apps with RubyMotion, albeit both were before RubyMotion added Android support (2013-2014. I subsequently rewrote one of those apps in ReactNative (replacing a Native Android app too), and I currently maintain and occasionally develop that cross-platform React Native app (though I’m currently in limbo because Apple started doing Section 4.2 rejections for my updates)
My 2 cents is that app development is just hard, compared to web development and the grass isn’t greener one way or the other, it’s just different.
With RubyMotion, I was writing against native APIs, just in Ruby. So reading Apple Objective-C System/UI docs and rewriting them into Ruby syntax. I dunno if you’ve run across this, but that’s me: Objective-C to RubyMotion Converter
I don’t have experience with RubyMotion for Android, but it looks like a similar thing: you’re taking Native Java APIs and interfacing with them via Ruby syntax.
So with RubyMotion, you’re still writing 2 different applications, but in the same language (I may be wrong on the current state of this; but that was the trend in 2014). But if your application is just some simple WebView wrappers, that might be fine. I found RubyMotion to be pretty stable and well supported (though not widely used).
With React Native, you are interfacing with React Native’s own UI API and most of a custom system API. You have to be aware of what’s that’s interfacing with at the lower native level, but it’s all abstracted and there is a huge mess of 3rd party libraries that also obfuscate it. Also, React Native has a brutal upgrade cycle that has me spending most of my budgeted time fixing build problems and updating breaking changes across libraries rather than introducing new features. It’s widely used, but the signal-to-noise ratio is terrible when you run into a problem.
It may not read like it, but I am happy with my ability as a solo developer to deliver a unified experience with React Native, but my expectations are very, very low.