developers ◦ Almost all web developer in Quipper can write React • Share some logics/UI components among Web and App • Easy to integrate with existing app
• Read “Integration with Existing Apps” section in official doc • Migrated to “monorepo” • Proceed a migration incrementally from new feature • The magic API: RCTRootView ◦ We wrap with UIViewController(ReactViewController)
ago ◦ NDK, slow in debug mode, lots of workarounds are needed ◦ Especially on “brown-field” app • Cross platform is apparently difficult ◦ Who knows both platform philosophies well? ◦ Few developers can write a bridge
it can’t be genuine “Single Store” ◦ Because existing code already has its own infrastructure • Don’t sync any data as much as you can ◦ Follow single-way sync direction if you really need to do ◦ We only sync essential user data(like userID) ◦ The magic API: RCTBridge, RCTDeviceEventEmitter
customView written in JavaScript” ◦ Use UIViewController for container/screen transition ◦ Easy to integrate with existing screens ◦ Easy to deal with new platform change(like SafeArea) • Still important to follow HIG/iOS standard way
2 Web devs, 1 iOS dev • React component and redux are loose coupling and testable • Performance is better than expected and no memory issue for now • We can share some logics/interfaces(not UI)
React Native is not a silver bullet • you can scale up a team by mixing web practice and iOS knowledge • If you develop “green field” app, Go! • If you develop “brown field” app, be careful for aforementioned points