From Native To React Native

Transcript

1. 1.

   FROM NSString *native TO <React.Native /> 28/04/2018

2. 2.

   @deVladinci

3. 3.

   None
4. 4.

   2015

5. 5.

   Version 2.0 ✅ ❌

6. 6.

   2016

7. 7.

   Version 3.0 ✅ ❌

8. 8.

   You want to be on as many platforms as you

   can.
9. 9.

   ?

10. 10.

    4% 77% 19% iOS Android Other Show how many users

    are on android mobile.
11. 11.

    Should we go Native or React Native?

12. 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. 13.

    Cons 1. Not a mature technology 2. Smaller community 3.

    Still need native devs at some point
14. 14.

    0 Lines of platform specific code

15. 15.

    None
16. 16.

    Structuring the Project

17. 17.

    –W.Edwards Deming “If you can’t describe what you are doing

    as a process, you don’t know what you are doing”
18. 18.

    None
19. 19.

    Components

20. 20.

    1. General components

21. 21.

    None
22. 22.

    1. General components 2. Wrap 3rd party libraries

23. 23.

    None
24. 24.

    1. General components 2. Wrap 3rd party libraries 3. Express

    domain concept
25. 25.

    None
26. 26.

    1. General components 2. Wrap 3rd party libraries 3. Express

    domain concept 4. Handle platform specific UI
27. 27.

    99% of the platform specific code is in Components

28. 28.

    None
29. 29.

    None
30. 30.

    Modules

31. 31.

    None
32. 32.

    Screen Action Reducer Selector Constants

33. 33.

    Navigation is a module

34. 34.

    None
35. 35.

    Navigation in Redux

36. 36.

    None
37. 37.

    None
38. 38.

    Thank you!