Designing for Ember Apps
summary
Ember design focuses on concrete patterns not buzzwords: it defines five major ones (gradual engagement, skeleton UI, carrying context, repeated core interactions, optimistic offline), demonstrates each with real apps (Pandora, Tinder, Pinterest, Spotify, Instagram, Threes) and shows where things fail (Google Docs connection blocking). A small open source pattern library called tools of the trade is underway with Ember code examples and methods, aiming to be reusable components and implementations that can be dropped into apps and verified in production.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:18Loading presentation...
- 1:36Designing for Single Page Applications
- 2:25Welcome to the world of making things for people.
- 3:14how I think the thing works
- 3:38Mental Models: can be updated/changed
- 6:35Micro Models how I think each individual interaction works
- 10:40Build a framework for understanding
- 11:45Use them explicitly If they directly apply
- 13:40Design Methods & Patterns
- 13:51Gradual Engagement reducing perceived risk
- 15:40Skeleton UI thinning out the spinners
- 17:55Carry Context be kind, don't rewind
- 19:29Can be a major save.
- 20:30Reuse Core Interactions cementing in that value
- 21:18Micro Macro core interactions become a symbol of your app
- 23:38Offline Mode "Goliath mode"
related talks
28mUnderstanding Ember with Design Patterns
32mEmber Between Design and Development
35mPanel: Ember – Why and Where?
26mCreating Fluid App-Like Experiences with Ember
24mNew to Ember: What ARE All These Things?
31mEmber on Rails: #REALTALK
29mIdiomatic Ember, Sweet Spot of Performance and Productivity
01h 10mPanel: the future of Ember