Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

React Native: Expectations vs Reality

115 views

Published on

I had a chance to be part of a team that started developing a decent size React Native mobile app from scratch. As a developer with a solid React background, I had some expectations at first. During my initial research, everything sounded terrific: performance stats, ease of development, learn-once-use-everywhere, debugging tools, etc. But is everything terrific really?

I'm excited to share my journey about how my expectations met the reality. I'll give my personal opinion about the matureness of the technology, for which use-cases it fits well and for which it doesn't. I'll also try to address the most popular misconceptions about React Native, which front-end developers usually have before they have the chance to actually built something.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

React Native: Expectations vs Reality

  1. 1. React Native Expectations vs Reality
  2. 2. CSS-Tricks
  3. 3. How about you?
  4. 4. Why I’m excited about React Native
  5. 5. Progressive Web App Mobile App Mobile App JavaScript Swift Java
  6. 6. Agenda! Expectations vs Reality for: 1. Learning Curve 2. Limitations 3. Debugging 4. Ecosystem 5. Performance
  7. 7. Introducing… our scale! 0 . . . . 5
  8. 8. #1 Learning Curve Expectation: 5
  9. 9. A lot of React concepts do apply!
  10. 10. Flexbox
  11. 11. Piniz a way to resolve a problem, usually technical and hidden
  12. 12. React Navigation
  13. 13. Write Learn once, use anywhere
  14. 14. Time-to-learn.
  15. 15. #1 Learning Curve Expectation: 5 Reality: 2
  16. 16. #2 Limitations Expectation: 4
  17. 17. “Pure” React Native React Native with “Create React Native App” and “Expo” vs. The decision.
  18. 18. Expo: NO native modules (without detaching)
  19. 19. Which compromises are you willing to do?
  20. 20. #2 Limitations Expectation: 4 Reality: 3
  21. 21. #3 Debugging Expectation: 5
  22. 22. Inspecting elements
  23. 23. Slooooow and it crashes often :(
  24. 24. Network Tab
  25. 25. #3 Debugging Expectation: 5 Reality: 1
  26. 26. #4 Ecosystem Expectation: 3
  27. 27. Multi-slider Component
  28. 28. Gallery Component
  29. 29. #4 Ecosystem Expectation: 3 Reality: 1
  30. 30. #5 Performance Expectation: 4 Reality: 5
  31. 31. #Sum up 1. Learning Curve 2. Limitations 3. Debugging 4. Ecosystem 5. Performance
  32. 32. Thank you. You were awesome! (I hope) superkalo.com

×