It's orders of magnitude more expensive for a company to have swift specialists, kotlin specialists, and js specialists for a user experience that is meant to be fluid (or at least consistent) across platforms. Design consistency ends up being manually maintained, which is extremely faulty.
My company uses react-native for iOS and Android, and it works pretty well. We sell a web product, but for certain use cases our users need to be able to use a phone or tablet without internet connection.
I'm really surprised Apple's not cracking down on react-native yet. I wonder if it's because they don't want to get in a fight with Facebook?
> I'm really surprised Apple's not cracking down on react-native yet.
Why is this surprising? React-Native uses JavaScriptCore, which Apple has promoted since long before iOS or any of their App Stores even existed. Apple isn't (AFAICT) rejecting any apps for using JavaScript under the covers.
The design should be consistent not across platforms but across the particular platform. Don't use Android conventions on iOS, don't use iOS conventions on Android.
My company uses react-native for iOS and Android, and it works pretty well. We sell a web product, but for certain use cases our users need to be able to use a phone or tablet without internet connection.
I'm really surprised Apple's not cracking down on react-native yet. I wonder if it's because they don't want to get in a fight with Facebook?