4 ms·

I was at the SF React Native developers meet up the other night, the speaker (Devin Abbott) gave several nice pro/con's slide re react native. Here's a picture

by htormey 10y ago

I was at the SF React Native developers meet up the other night, the speaker (Devin Abbott) gave several nice pro/con's slide re react native. Here's a picture of the slides: http://imgur.com/a/T3O7i http://imgur.com/a/T3O7i http://imgur.com/a/z2oIU http://imgur.com/a/z2oIU

what2 10y ago
Awesome, thanks! Right now I will wait a little more and see how the tech evolves. Been burned by too many miracle technologies
- htormey 10y ago
  Yeah, it really depends on what your needs are. React Native has a lot of cool features but it also has quite a steep learning curve if you are new to React or new to Native development.
tedmiston 10y ago
Great comparison. Slides transcribed: -- Slide 1 -- Maybe we should use React Native: - We know JS / React - We have lots of web developers but few mobile - Our design is brand-focused - We're willing to invest in RN - We want to get into OSS - We want OTA code updates Or maybe we shouldn't: - We don't know JS / React - We already have an iOS team and an Android team - Our designs are heavily platform-specific - We don't have the time or money for an RN team / OSS -- Slide 2 -- Pros: - Cross-platform - Performant, native feel (with some effort) - Great developer experience - Push updates over-the-air - Strong community - Backed by Facebook Cons: - Early - Unstable (bugs, APIs) - Ecosystem not fully developed - Polished apps are high effort - You may need native code (so JS + Obj-C + Java)
- gaza3g 10y ago
  Thanks for this. The thing that captured my interest was the point about being backed by Facebook. Parse was backed by Facebook and look where it is now.
  - eclout 10y ago
    I don't think Facebook backing Parse is relevant. React Native was designed by Facebook, so I'm assuming they understood the design choices of the mobile ecosystem at the time. Parse was an acquisition by Facebook that didn't end up working out.
    - spicyj 10y ago
      I'll add that we use RN in our production apps and are building it for ourselves but never used Parse in the same way.

by htormey 10y ago

what2 10y ago

Awesome, thanks! Right now I will wait a little more and see how the tech evolves. Been burned by too many miracle technologies

htormey 10y ago
Yeah, it really depends on what your needs are. React Native has a lot of cool features but it also has quite a steep learning curve if you are new to React or new to Native development.

tedmiston 10y ago

Great comparison. Slides transcribed: -- Slide 1 -- Maybe we should use React Native: - We know JS / React - We have lots of web developers but few mobile - Our design is brand-focused - We're willing to invest in RN - We want to get into OSS - We want OTA code updates Or maybe we shouldn't: - We don't know JS / React - We already have an iOS team and an Android team - Our designs are heavily platform-specific - We don't have the time or money for an RN team / OSS -- Slide 2 -- Pros: - Cross-platform - Performant, native feel (with some effort) - Great developer experience - Push updates over-the-air - Strong community - Backed by Facebook Cons: - Early - Unstable (bugs, APIs) - Ecosystem not fully developed - Polished apps are high effort - You may need native code (so JS + Obj-C + Java)

gaza3g 10y ago
Thanks for this. The thing that captured my interest was the point about being backed by Facebook. Parse was backed by Facebook and look where it is now.
- eclout 10y ago
  I don't think Facebook backing Parse is relevant. React Native was designed by Facebook, so I'm assuming they understood the design choices of the mobile ecosystem at the time. Parse was an acquisition by Facebook that didn't end up working out.
  - spicyj 10y ago
    I'll add that we use RN in our production apps and are building it for ourselves but never used Parse in the same way.