You want to have logic in your application that responds to browser resizing that matches your CSS media queries.
Use a service to watch for the resize event and set variables that can be accessed throughout your application.
Now you can access Resolution from inside your templates, controllers, and components
From within a template:
From within a controller or component
Ember.js can inject services where needed. In this example we are injecting Resolution to our components and controllers. This will allow us to have logic based on resolution (ex. rendering a graph only on desktop). We are using matchmedia which supports everything upwards of IE 9. This approach will follow your CSS media queries where something like $(window).width will not. By debouncing the resize event this will increase performance by only calling environmentCheck once after one second from the last resize event. If you absolutely need to support IE you can check out Modernizr’s mq().
If you need to have logic for mobile and tablet or tablet and desktop you could easily add a computed property based on isMobile, isTablet, and isDesktop