From Native To React Native

Talk on ReactNotAConf 2018 Edition.

1. FROM NSString *native TO <React.Native /> 28/04/2018
2. @deVladinci
5. Version 2.0 ✅ ❌
7. Version 3.0 ✅ ❌
8. You want to be on as many platforms as you can.
9. ?
10. 4% 77% 19% iOS Android Other Show how many users are on android mobile.
11. Should we go Native or React Native?
12. Pros 1. The whole team can maintain the codebase and contribute 2. Cross-platform 3. Compiles to native code 4. Reuse existing native and web logic 5. Speed up development
13. Cons 1. Not a mature technology 2. Smaller community 3. Still need native devs at some point
14. 0 Lines of platform specific code
16. Structuring the Project
17. –W.Edwards Deming “If you can’t describe what you are doing as a process, you don’t know what you are doing”
19. Components
20. 1. General components
22. 1. General components 2. Wrap 3rd party libraries
24. 1. General components 2. Wrap 3rd party libraries 3. Express domain concept
26. 1. General components 2. Wrap 3rd party libraries 3. Express domain concept 4. Handle platform specific UI
27. 99% of the platform specific code is in Components
30. Modules
32. Screen Action Reducer Selector Constants
33. Navigation is a module
35. Navigation in Redux
38. Thank you!