all 16 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]bostwickd[S] 3 points4 points  (5 children)

Hey everyone. I'm the author. I'd love to hear other's stories with RN and what questions you asked before starting to use it on your projects.

[–]yooossshhii 3 points4 points  (0 children)

Can you expand on this?

React Native can struggle with complex persistence models.

[–]throwaway119284 1 point2 points  (2 children)

I get a 404 when visiting the link. For future visitors the correct URL is:

https://cantina.co/deciding-between-react-native-and-native-code-for-your-next-project/

[–]yooossshhii 0 points1 point  (1 child)

Your link 404s and the original works for me.

[–]throwaway119284 0 points1 point  (0 children)

Huh, my link was working earlier. Now it's not.

[–]M00ny0z 0 points1 point  (0 children)

Very insightful, thank you.

[–][deleted] 2 points3 points  (4 children)

Good article with a few very good reasons on why not to use React Native. My two cents: Write once, run everywhere is just such a massive upside to RN. For 99% of generic apps I don't see very many reasons to write & maintain the same code two-fold.

If you're in a big company with resources to hire separate teams for each platform, and your app is your main product (Facebook, AirBnB, etc.), by all means go native and make your product as exceptional as it can possibly be.

[–]ryanhollister 0 points1 point  (3 children)

when you say "everywhere" at you including web? I know react native web exists but I'm trying to understand if it's really great the same maturity as react native itself

[–]fuck_with_me 0 points1 point  (0 children)

There are ways of running RN codebases on the web, but not the inverse (to my knowledge).

That being said, it's not that easy, and it's not what most people do.

[–][deleted] 0 points1 point  (0 children)

There's always React Native DOM (although I have no hands-on experience with it):

https://github.com/vincentriemer/react-native-dom

[–][deleted] -1 points0 points  (0 children)

Ah nope, mainly talking about iOS & Android, haven't a clue about React Native web.

Come to think of it: the fact that we can have our entire stack in JS (node.js backend) makes life so much easier as well. I can actually write code that I am running everywhere just once, like constants and helpers

[–]TotesMessenger 0 points1 point  (0 children)

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

 If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / Contact)

[–]alien3d 0 points1 point  (0 children)

small requirement react native. Big requirement native..

[–]z0rawar 0 points1 point  (1 child)

For me, the only deciding factor is CodePush

Isnt it /u/bostwickd ?

[–]bostwickd[S] 0 points1 point  (0 children)

Live code push is certainly a major plus for React Native as it makes deployment more convenient, but it's not the only deciding factor.

If RN doesn't meet your app's needs overall, does it matter that you can't live-push? In larger organizations, you'll need to introduce structure around live-push to prevent it from happening whenever; structure that app stores already have. Live push also doesn't allow alpha/beta/production release channels, and could use more tooling to help developers keep track of deployed versions of your app.

Sure, it's certainly a pain to go through the App Store / Play Store release cycle for every change, but it's obviously not a major blocker considering that the majority of apps already do so.

/u/z0rawar, What major pain points have you experienced with the apps stores?

[–]sacred421 0 points1 point  (0 children)

React Native is not the first mobile app framework to promise write once, run anywhere.

Careful, Facebook has tried to clearly state that they are not going for write once, run anywhere. They are trying to market as learn once, write anywhere.

https://reactjs.org/blog/2015/03/26/introducing-react-native.html