Download as PDF, PPTX
Uploaded byEugene Zharkov
Monorepo: React + React Native. React Alicante
The document discusses the integration and development challenges faced in building web and mobile applications using technologies such as React, React Native, and various other frameworks. It highlights issues related to code sharing, dependency management, and the need for platform-agnostic core code, while emphasizing the importance of team dynamics and communication with stakeholders. Recommendations are provided to address potential issues and ensure a smoother development process.
More Related Content
![5 Reasons Why Your Website Is[n’t] a Native App (PrDC 2015)](https://cdn.slidesharecdn.com/ss_thumbnails/5reasonswhyyourwebsiteisntanativeapp-150604163105-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Monorepo: React + React Native. React Alicante
Monorepo: React + React Native. React Alicante
- 3. OUR AMAZING TEAM BackendDeveloper Eugenio Frontend Developer Yevhen Mobile Developer Eugene There is no limit if logic
- 4.
- 5. write applications…obviously hire teams consult makeworkshops…sometimes own the dog I
- 6. OK… 1 repo React +React Native ideas…
- 8. Where are you Buildingfrom scratch Web application is ready Mobile application is ready Mobile & Web applications are ready
- 9. Classic Case iOS AndroidWeb Product
- 10. Technologies iOS Android Web Swift/ Objective-C Java / Kotlin Java Script React Angular Vue Ember Elm Svelte TypeScript jQuery ;) and much more
- 11.
- 12.
- 13. React Promise React Team TeamLead Product Owner Native Team
- 14. Issues • Technologies • Tasksynchronization • Delivery synchronization • Hiring • People, people, people
- 15. How do yousolve all those issues?
- 16. React Promise • Onelanguage - JavaScript / TypeScript • Single UI library - React • 1 or 2 teams • Less expertise for hiring • Share code between Web and Mobile
- 17. There is noMagic Wand
- 18.
- 19. Issue #0 You needto share a code between web and mobile. Shared Web Mobile
- 20.
- 21.
- 22.
- 23. Issue #1 Metro bundlerdoesn’t support symlinks
- 24. Issue #2 Build -OK Development - NOPE OK NOPENOPENOPENOPE
- 25. WML by WIX Copieschanged files from source to destination folders
- 26. Issue #3 Last update2 years ago Unstable
- 27.
- 28.
- 29. Specify any additional(to projectRoot) watch folders, this is used to know which files to watch.
- 30. Which other node_modulesto include besides the ones relative to the project directory. This is keyed by dependency name.
- 31.
- 32. Lerna Tool for managingJavaScript projects with multiple packages.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. Issue #4 Core codeshould be platform agnostic
- 41.
- 42. React Native forWeb💪 💪
- 43. Browser React HTML & CSS TC39Browser implementation babel anyother bug Markup
- 44. Mobile Platform React Native ReactNative for Web React Browser
- 48. Potential issues • ReactNative bugs, controls and behavior issues • React Native for Web bugs, limits, interpretation • 3rd party components and markup control • Styling • Integration
- 49. Issue #5 Web andMobile application should behave similar React Web React Native
- 53.
- 54.
- 56. What to expect •Data loading strategy can be different • Data source structure can be different, SectionList for example
- 57. The End • Keepyour estimates real • Check the idea before “yes, we’ll do it” • Talk to your Product Owner, share the potential issues and limits • Relax and write the code
- 58.