More Related Content
What's hot (20)
Viewers also liked (20)
![[React Native Tutorial] Lecture 6: Component, Props, and Network](https://cdn.slidesharecdn.com/ss_thumbnails/l6-component-prop-network-160920050452-thumbnail.jpg?width=560&fit=bounds)
![[React Native] Lecture 4: Basic Elements and UI Layout by using FlexBox](https://cdn.slidesharecdn.com/ss_thumbnails/l4-react-native-layout-160911060742-thumbnail.jpg?width=560&fit=bounds)
Similar to Getting Started with React Native (and should I use it at all?) (20)
Recently uploaded (20)
Getting Started with React Native (and should I use it at all?)
- 1. Getting Started with React Native
- 3. • Cross-platform • Performant, native feel (with some effort) • Great developer experience • Push updates over-the-air • Strong community • Backed by Facebook Pros • Early • Unstable (bugs, APIs) • Ecosystem not fully developed • Polished apps are high effort • You may need native code (so JS + Obj-C + Java) Cons
- 4. • 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 Maybe we should use React Native • 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 Or maybe we shouldn’t
- 5. Resources
- 6. The RN Docs
- 7. Exponent
- 9. Communities
- 10. React Native Community Facebook Group
- 12. Exponent Slack
- 13. Boilerplates Ignite - 3,607 stars Pepperoni App Kit - 2,975 stars Snowflake - 2,885 stars Create React Native App
- 14. • We want to start coding now • Optimize for short term • Large team starting today • We don’t know how to setup redux + navigation + … • We don’t mind accruing a bit of technical debt Maybe we should use a boilerplate • We want to spend a few days learning foundations • We have a small team • We’re experienced with the modern JS / React stack • We want to choose exactly the right libraries for our app Or maybe we shouldn’t
- 15. FAQ
- 16. Which navigation library should I use? react-navigation* *if you absolutely need native navigation: react-native-navigation
- 17. Should we use Flow? I recommend no Flow to begin with • Fewer things to learn • Less code to write • Tooling isn’t quite there • Can add incrementally later
- 18. Should we learn React JS before React Native? Sort of Typically "React JS" means React for the web. The web-specific stuff is not relevant (e.g. DOM elements and browser APIs). The React fundamentals are the same for web and mobile though (component lifecycle, etc), and you will need to learn those.
- 19. Can we re-use code between web and mobile? Sort of Certainly most of the non-React code can be re-used. If you want to literally write the same app for both web and mobile, there are two libraries to consider using: react-native-web and react-primitives. These both provide components that work on web and mobile. You could also just re-use a subset of your components that don’t render primitives (div, View)