I’m a long time Objective-C and Swift developer...I’ve been asked to “research” a project using React Native.

It felt dirty to be writing an iOS app using JavaScript.

I’m still not sure why and how React Native is better/faster than native Swift.

Someone change my mind...

@Pseudonymous That post doesn't make any sense. Many native modules rely on native code (Both from Java and Swift).

So React-Native maybe have similar performance as native app, but it can never faster than native app.

@iosnerd It's not better. It's not faster. It's simply easier to implement and has shorter development cycle.

"Someone change my mind"

What about no.

Ok it's not faster. HOWEVER being a bundled js file as they call it. It doesn't require code sign off and all that Apple bollocks. You can use codepush to update your bundle, do AB testing and all that sort of stuff which is great when you've got that "could you change the colour" type client that really gets on your tits.
You can also version releases with code push, rollback etc.

There's a lot of easily integrated packages that can set themselves up using link and shit.

Anyway. I think it comes down to personal preference. For me I can use react native web, build my website and app in one go pretty much. I don't know objective C or know java that well so I can build basic apps that function great without learning a new language. SO YOU could give your app to a junior to work on and know they'll probably be fine without supervision.

I hate anything development from Facebook. React Native is shit in comparison to native Kotlin/Swift. I swore never to write JavaScript code for mobile.

1. Using React Native = Writing once and running on both platforms

2. React Native is good, has good performance but Native is for sure better, I tried loading a list with 10 items on RN it takes couple of seconds to open the new ViewController and display list items, while in Native code (android & iOS) it happens instantly

3. Maintaining code on RN is better NOT BECAUSE RN IS BETTER but because same code base for both platforms, while native, needs to go through the process twice.

For I'd never use React native for mid/large projects, but for a small one then why not, it gets the job done in no time and for both iOS and Android.

@gitpush

"I'd never use React native for mid/large projects"

'nuff said

Because it is very easy to port them to Android/Ios with little to no effort, and if there’s a performance sensitive part, you can put native code, and it will still remain quite maintainable

It’s not. It just allows business not to spend money on developing two separate apps and just hire minimum wage js developers to develop only one app and then build it for both android and iOS.

It’s reasonable enough for burger place app, but for nothing more.

Native is obviously faster, but in some aspects, React-Native actually comes close to native speeds. Only downside you'll find currently is that there is a small delay when you startup your application. React Native is just a react-like abstraction over native components.

Wow, thanks for all the input and comments! I really appreciate it! It’s all great info!

This is for a large scale enterprise app that will run on iPads and web. I have my hesitations of doing it this way but the company is trying to save money and Dev time, but I feel like using RN in this manner is not long term sustainable and 100% dependent on an open source platform that could be deprecated at any point *cough* Parse *cough*

I personally have found using JavaScript and RN just clunky to work with and it’s no match for using Swift with Xcode.

Hopefully I can change my directors mind...soon.

@iosnerd I hope you don't try Java then 😅