The key to building and maintaining users' confidence in long running applications is fault tolerance. Not just a data and connectivity concern - fault tolerance should be considered at every level of your application. A fault tolerant application clearly conveys its state to users throughout its interface, allows users to remain as productive as possible in any particular state, and ideally works behind the scenes to recover from faults.
This talk will cover UX patterns and engineering strategies for building fault tolerant Ember.js applications.
Ember, to help us build apps today, has provided its own version of many ES6 and ES7 features. As the drafts become specs and browsers add new capabilities, the framework will need to reconfigure itself around them.
How well does Ember align with these new APIs? Where the framework differs, what might be a path forward?
Ember has technology’s most loveable mascot. He’s approachable, thoughtful, and never takes himself too seriously. Our community is like that too.
In this talk, we’ll learn the story of Tomster: where he came from, how he’s grown, and what he represents. Then we’ll zoom out and see how the minds that gave us Tomster have carefully crafted a framework for creating communities like ours. Finally we’ll zoom back in again to see how to use that framework on a local scale to grow the Ember community worldwide.
You've heard the hype about web components, but what does the spec provide other than small, re-usable chunks of markup?
Web components provide an incredibly powerful and declarative way of structuring web apps. The Polymer platform in particular holds many hidden secrets, including a paradigm shift for interaction design: an animation library that bridges the gap between application states, providing a sense of context and clarity of purpose as you move through an app experience.
We will show you how to leverage the power of Ember 2.0 and Polymer to create remarkable user experiences.
This presentation will highlight how to extend Ember CLI through add-ons, explaining example use-cases, how to create one, and the hooks available for developers to build into.
Coming to Ember from Rails means entering a world where familiar terms mean unfamiliar things - "router", "controller", etc. I'll be focusing on some specific examples where assuming the "Rails meaning" really threw me off track when learning Ember, and demonstrating how approaching things with an open mind can improve your code.
Definitely tune into my presentation if you're interested in ways to best integrate your application with analytics and reporting suites such as Google Analytics and Adobe SiteCatalyst. Our company is going to be utilizing SiteCatalyst so that may end up being more of the focus area, but I should be going into details and best practices about ways to track pageviews, user interactions, and other web tracking considerations.
Computed properties are an important feature for any ember.js developer to master. This talk offers an overview of a particular subset of computed properties: array computed properties, which allow for partial recomputation. This is the feature that saves, for instance, `Ember.computed.filterBy` from having to completely recompute the filtered array when an item is added to its dependent array.
A breakdown of the general architecture that was used for building CloudHdr. The entire system is composed of 3 main "service" apps, and a collection of Ember apps each aimed at a different vertical slice of user facing functionality. Topics include auth from the Ember apps to services, cross domain issues for data transfer, and handling file uploads.