Can someone advise on the best approach to developing an Ember.js app that needs to interact with external code, such as being called from an Android app through a WebView or other sources outside of the Ember Application's scope?
In such cases, having a clear public interface between the JavaScript and Java worlds is crucial. This interface could be an encapsulated object that allows the Ember.js router to respond to changes in the application state. While AngularJS seems to handle this type of scenario well with services and Dependency Injection, it's not as straightforward in Ember.js. What mechanisms does Ember.js provide for creating an external interface between the App and the outside world?
While there are potential workarounds like using App.container, I'm seeking a solution that aligns with the framework's intended design principles. I don't want to end up battling against the framework I choose. That's why, for this specific project, I'm considering using a less opinionated framework like Backbone.js, even though I appreciate the overall organization of Ember.js based on my limited experience.