Two Ember Apps Become One
summary
Phorest embeds an older Ember app inside a new Ember host via an iframe and coordinates routing with postMessage and event listeners so the host root mirrors the embedded app, using a boot handshake, a single iframe override stylesheet to standardize styles, and Ember Browser Services to swap sessionStorage/localStorage for testable browser APIs. Built auto-login links and an Electron path while noting competitors lost 10% of customers and 65% of users expect desktop+web; the merge works and preserves UX during migration.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:30Background
- 6:59Legacy
- 10:12Two Ember Apps
- 11:33How Ember Apps Boot
- 12:35Rooting Ember Apps
- 13:48Updating Ember Apps URL
- 14:29Embedded App
- 15:00Helper
- 16:39Ember Browser Services
- 17:22iframe override style sheet
- 17:52Compare and contrast
- 18:35Zoe
- 18:48Summary
- 19:31Market Research
- 20:50Embedded Apps
- 23:09Appointments
- 24:26Conclusion
related talks
51mWrite once, run everywhere: ambitious cross-device web apps
24mMigrating an Existing App to Ember, Component After Component
35mPanel: Ember – Why and Where?
30mReact + Ember A Practical Guide to Micro Frontend Integration
25mThe Chirpolith: Successfully Migrating a Messy App to Ember
41mWeb, Native iOS and Native Android with one Ember js App
25mThe Great Migration, Redesigning and Rewriting our App in Ember.js
25mFramework Freedom with Micro Frontends
