Talk on ReactNotAConf 2018 Edition.
FROMNSString *nativeTO28/04/2018
View Slide
@deVladinci
2015
Version 2.0✅ ❌
2016
Version 3.0✅ ❌
You want to be on asmany platforms as youcan.
?
4%77%19%iOS Android OtherShow how many users are on androidmobile.
Should we go NativeorReact Native?
Pros1. The whole team can maintain the codebase andcontribute2. Cross-platform3. Compiles to native code4. Reuse existing native and web logic5. Speed up development
Cons1. Not a mature technology2. Smaller community3. Still need native devs at some point
0Linesof platform specific code
Structuring theProject
–W.Edwards Deming“If you can’t describe what you are doing as aprocess, you don’t know what you are doing”
Components
1. General components
1. General components2. Wrap 3rd party libraries
1. General components2. Wrap 3rd party libraries3. Express domain concept
1. General components2. Wrap 3rd party libraries3. Express domain concept4. Handle platform specific UI
99% of the platform specific code isin Components
Modules
ScreenActionReducerSelectorConstants
Navigationis a module
Navigation in Redux
Thank you!