Controlling Route Traversal with Flows
summary
Builds a concrete claim: route traversal is driven by a tree-shaped state machine loaded from a single flow definition rather than scattered route logic, handling about eighteen permutations of an online-banking login. Uses Ember CLI, session injection, beforeModel redirection, and browser-friendly navigation with replaceWith. Demoed a working Ember app that loads flow state, calls the server for validation, saves progress, uses Google's libphonenumber, and successfully traverses to the correct account page.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:37URLs as API
- 2:03Resources vs action routes
- 4:57Flows for multi-route actions
- 7:06Modeling flows correctly
- 8:08Inventory routes step-by-step
- 10:16State changes for traversal
- 11:44Back navigation in flows
- 13:10State machine benefits
- 14:15Ember Router and async
- 15:20Demo: online banking flow
- 19:00Naive flow traversal
- 21:11replaceWith for history
- 22:39Flow-based traversal improved
- 24:24Flows with edge lists
- 25:48Injecting flows into routes
- 26:52Ember Flows project
- 27:34Q&A
related talks
26mInteraction Design with Ember 2.0 and Polymer
27mOn the Development of Reactive Systems with Ember.js
31mBest Practices for Architecting Server-Driven Web/Mobile Apps
31mEmber on Rails: #REALTALK
26mCreating Fluid App-Like Experiences with Ember
24mNew to Ember: What ARE All These Things?
46mArt and Science of Shipping Single Page Apps with Ember.js
32mAn Animated Guide to Ember Internals