Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Learn Once, Write Anywhere: Intro to React Native

Learn Once, Write Anywhere: Intro to React Native

Facebook has gifted the world with a new way to develop native mobile applications using JavaScript: React Native. This doesn't sound like a very revolutionary concept, but the way Facebook chose to do it makes React Native stand out among its peers. In this talk, we’ll take a look at what RN is, how it differs from its competition, and why we might want to use it. Geared toward developers with limited or no experience building mobile applications, it takes a high level view of the framework and makes a compelling case for considering it as part of your toolset.

Aaron Greenwald

April 05, 2016
Tweet

More Decks by Aaron Greenwald

Other Decks in Technology

Transcript

  1. “A framework for building native apps with React” - Facebook

    Very popular, but very young and unstable
  2. Wait...this isn’t new let [ PhoneGap, Trigger.io, Cordova, Ionic, Sencha

    Touch, Kendo UI, Appcelerator Titanium, Xamarin ...rest ] = stuffWeTriedBefore;
  3. Develop quickly Use the richest ecosystem there is Smoother transition

    from the web Deploy like you’re on the web
  4. Develop quickly Deploy like you’re on the web Use the

    richest ecosystem there is Smoother transition from the web Learn Once, Write Anywhere
  5. Develop quickly Deploy like you’re on the web Use the

    richest ecosystem there is Learn Once, Write Anywhere Smoother transition from the web Reuse code
  6. You can’t always code push. Sometimes you need to change

    binaries. It’s Still Not Web Development
  7. You can’t always code push. Sometimes you need to change

    binaries. Styling is different. Presents a learning curve. It’s Still Not Web Development
  8. You can’t always code push. Sometimes you need to change

    binaries. Styling is different. Presents a learning curve. Platform-specific thinking. Adapt requirements and mindset for mobile. Debugging isn’ t the same. It’s getting better, but slowly. It’s Still Not Web Development
  9. It’s Still Not Web Development You can’t always code push.

    Sometimes you need to change binaries. Styling is different. Presents a learning curve. Platform-specific thinking. Adapt requirements and mindset for mobile. Debugging isn’ t the same. It’s getting better, but slowly.
  10. • Many poorly solved problems • No consensus on best

    practices • Instability • Large community • Many solved problems • A chance to get involved
  11. • Many poorly solved problems • No consensus on best

    practices • Instability • Large community • Many solved problems • A chance to get involved If your scale is relatively small, stick to traditional native
  12. • Reuse web developers’ skills • Transition quickly between web

    and mobile • Deliver amazing mobile apps • Many poorly solved problems • No consensus on best practices • Instability
  13. • Reuse web developers’ skills • Transition quickly between web

    and mobile • Deliver amazing mobile apps If you’re Wix, you don’t really have a choice • Many poorly solved problems • No consensus on best practices • Instability