Ember is "the framework for building ambitious applications." But what happens when that ambition leaves some users behind? For many in the enterprise environment, accessibility is a legal requirement. For anyone building a new app elsewhere, the user data speaks for itself: nearly 10% of all users have some sort of a disability. So how can we make this easier? What already exists?
Not only will we discuss how Ember supports this, we'll look at some imaging techniques being used in scientific research that may help us look at this challenge from a different angle.
The "Grand Testing Unification" is finally here! In this talk you learn how to use the new QUnit testing APIs and we discuss why they were changed and what steps you need to take to migrate your existing tests to the new APIs. Finally we will look at the Ember ecosystem and introduce addons that can make your tests better than ever before.
The Ember community describes a worldwide subculture consisting of developers, contributors, bloggers, event organizers, podcasters and many others involved in activities around the framework. But which factors drive this complex community in its efforts?
After a retrospective of open-source activity in the ecosystem, we’ll see which core resources and addons are particularly popular and which topics are particularly interesting to the community. Summing up these findings, we’ll finally try to answer how diversity and growth of this community can be furthered even more in the future.
Acceptance tests are a wonderful way to describe how our apps behave at a high level, but what if they could say more? What if they could also say that our apps are intuitive, accessible, localised, and fast? What if they could say all this without any extra code?
In this talk we’ll imagine a set of hooks which allow us to build new layers of meaning into the test helpers we know and love. Then we’ll set about actually building them.
Ember's new filesystem layout, commonly called Module Unification, has arrived. Applications and addons alike have started to adopt the new convention. Why should you be looking at Module Unification? With the new layout we're bringing code bundling, improved namespacing for components, and a better integration path for addons to the framework.
"Building forms in @emberjs is terrifying because I'm stuck with decisions I always later regret." —me in another lifetime
Many companies that integrate Ember into their stacks often have a hard time finding quality developers in an ever-changing job market. Because of this, we often resort to training new developers in-house on the ways of Ember and Glimmer. Yet, what is the most effective way for us to hire, teach, and train developers in this aspect? I want to offer some practical advice, stories, and lessons learned from my experience with this over the past few years.
Most animation on the web is canned, non-interactive, and inflexible. It doesn’t dynamically adjust itself to changing conditions and user interactions. It’s expensive to create and maintain because the programmer or designer is trying to micromanage the motion. It needs to be hand-tuned for each new feature, device, or media query breakpoint.
There is an alternative: we can think more like game designers. We can build robust, dynamic systems that animate gracefully, with clear separation between app logic and app motion.
This talk will provide an overview of the latest developments in the realm of managing data in Ember applications. The focus will be the past, present, and future of Ember Data, which is becoming faster, lighter-weight, and more modular.
The JSON:API specification, which provides the conventions that underpin Ember Data, is evolving through “operations” and other extensions. And new interfaces are being explored in Ember Data to allow interop with Orbit.js, which will unlock capabilities such as offline operation, store forking / merging, and more.
If Beethoven was alive today, he’d probably use Ember. Using Ember, socket.io, the web audio API, and devices in the audience's pockets, we'll interactively explore the challenges of creating a real-time and audience-driven musical performance, different parts of which are played across a symphony of all phones in the audience.
When building app after app at what point do you stop mining your past projects to quickly prototype and commit to maintaining a configurable product? This is a story of building a successful digital agency in a sea of tech startups by figuring out how to transition from one-off Ember SPAs to maintaining reusable products.
Advance your Ember events knowledge from entry-level to expert in 30 minutes! Start with the basics of DOM events, learn the lifecycle of event listeners in Ember, then peek under the hood to understand how Ember handles clicks in your application. What are the different ways of listening for events in Ember? How do they interact? What are the performance implications of each approach? What kind of bugs can you introduce if you don't understand them?
You'll be able to implement event listeners with confidence and debug with clarity once you have a complete mental model of Ember events!
In 1945, the Memex was proposed as the ultimate personal library. In addition to storing information, users could navigate, organize, link, and share data with others.
Tragically, zero of these devices were ever produced, but 72 years later, I’ve build my own Memex in Ember. I’ve created dozens of importers for different services, organized the 10M+ data points into a graph schema, and built a frontend with Ember. Almost all aspects of my personal history is available through this app.
I’ll go over the history of the Memex, how I used Ember to build my own, and demo what I can do with it.
When your code doesn't work the way you expect, it could be a frustrating exercise to figure out what exactly went wrong. In this session, we will walk through the process of debugging an Ember app. Along the way, we will learn about some of the tools and techniques that could help shed light on the behavior of our code. Finally, we will also take a brief tour into the Ember codebase to look for clues.
Upon completing this orientation, you will be well-equipped to pry open the mysterious black box the next time your app misbehaves!
Mobile apps have UI patterns and features not often found in (mobile) web applications. We will take an in-depth look at ways to enhance user interaction for responsive Ember applications without having to develop a completely separate application.
Topics include application organization, templating concerns, interaction patterns, relevant addons and a display of newly built Ember addons to fill in for missing interaction features.