Bridging the gap between mobile web and native development
summary
Shows how to build real calendar plugins end-to-end: a Cordova plugin (JS + Objective‑C + Java) and a React Native native module (iOS + Android). Uses Cordova CLI, plugin.xml and cordova.exec; Cordova example is ~100 lines total with one class per platform and works in iOS and Android simulators returning strings like “registered in iOS.” Uses RCT_EXPORT_MODULE, Android Package + ReadableMap/WritableArray and Promise-style methods; Cordova plugin: ~100 lines, one class per platform React Native: RCT_EXPORT_MODULE, Promise-based native methods Demo: button calls native calendar API and returns native data to JS.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:03Why bridge web and native
- 2:50Hybrid app approaches overview
- 7:05Building a Cordova plugin
- 17:19JavaScript bridge implementation
- 24:11Introduction to React Native
- 28:30React Native project setup
- 31:22React Native iOS bridge
- 36:23React Native Android bridge
- 42:48Key takeaways and comparisons
- 46:25Q&A session
related talks
37mGetting to the Native in React Native
27mBuilding high quality mobile apps with React Native
50mBuilding Cross Platform Native Mobile Apps using React Native
36mThe journey through the hybrid mobile apps with JS
29mOrganizing Code for Cross-Platform Web and Mobile Development
48mWhy the transition from Apache Cordova to React Native is inevitable
36mCross-platform: ReactNative, Jamstack, And Beyond
35mBridging the Gap: How to use React Native in existing large native code bases
