Yeah, thanks for the quick replies. From what I’ve read “embedded” seems to imply that an application (only one) is just stuck inside of another server-rendered application. This is not that scenario.
It’s unfortunately more of a many nested client-side application scenario. There will be between 10, 50, potentially hundreds of applications available for a user to take advantage of, each with different functionality. So, one application may need to be utilized inside of another (B “inside of” A), or the nested relationship could be reversed (A “inside of” B). The nestedness really needs to be independent of the API/framework. I need to “stick” an application into the DOM wherever it needs to go, independent of whether the framework plays well with it being at that particular location.
I’m fine with having to program around the root url location of where the application and/or component should be rendered, but Ember seems to be generally incapable of nesting one application inside another.
Realistically, I need to nest the applications (or components of the application) at least up to 5 levels deep.