Turbolinks 5: I Can’t Believe It’s Not Native!
summary
Claim: Turbolinks 5 lets small teams ship lightning-fast Rails apps and high‑fidelity hybrid iOS and Android apps using a shared set of web views. Evidence: Basecamp 3 is built in 18 months with six Rails, two Android, two iOS devs, >200 screens and five platforms (desktop web, mobile web, iOS, Android, email). Details: Turbolinks 5 with iOS/Android adaptors uses a single shared web view and native chrome, requires ~30 lines to wrap the whole app, yields perceived navigation around 300 milliseconds and native transitions ≈315ms.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:07200+ screens
- 1:52Action Cable
- 7:21Conway's Law
- 10:34Single-Process Model
- 11:42Good Enough Performance
- 13:46Hybrid Sweet Spot
- 25:43Native app in 10 minutes
- 26:13Hybrid apps are custom browsers
- 28:52Choose what you optimize
related talks
24mTurbolinks, native with a trick?
28mJust enough Turbo Native to be dangerous
14mRails 5, Turbolinks 3, and the future of View-Over-the-Wire
30mUse Turbo Native to make hybrid apps that don't suck
40mOptimize for developer speed
01h 53mHotwire Native: A Rails developer’s secret tool to building mobile apps
34mInsights Gained from Developing a Hybrid Application Using...
01h 03mOpening Keynote