Making hybrid apps that don't suck
summary
Shopify builds a mobile hybrid called Sell app that keeps the web as the single source of truth, avoids any local DB, and limits native code to wiring and navigation. A tiny injected bridge object nativeApp plus an event hub (async Pub/Sub) passes JSON events between WebView and native controllers/fragments. Rails serves variant views based on a User‑Agent with app/platform/version; validation, form handler, console.log hijack, and Hockey/TestFlight crash collection handle errors.
AI-written summary · about
chapters (12)
- 0:00Introduction to hybrid apps
- 3:27Key goals for hybrid development
- 5:11Types of mobile apps compared
- 6:57Myths about hybrid apps
- 8:00Sending events from web to native
- 10:47Identifying app requests in Rails
- 17:11Event Hub for native-web communication
- 23:33Loading pages in hybrid apps
- 27:25Navigation in hybrid apps
- 31:36Handling form submissions
- 36:10Tracking and handling errors
- 41:26Summary and Q&A
related talks
34mInsights Gained from Developing a Hybrid Application Using...
20mDissolving Boundaries: The Fusion of React app and Native Apps!
27mReact Native: From pure Web app to a Web & Mobile hybrid
48mMobile Apps with JavaScript - There's More Than Web
35mReact Native & Rails, A Single Codebase for Web & Mobile
30mEnterprise Hybrid Mobile App development
40mIts fairy tale time: hybrid app development
25mOne Source to Rule them All
