Some improved interaction that is perceived as simple and easy like changing the location of a button ends up being technically unfeasible or too costly. Software development is an art/science of trade-offs where a combination of requirements lead to decisions that optimize an application for certain types of changes and make other types of changes impossible or too costly. In this series of articles developer Jaime González Garcia, attempts to be developer and UX Designer and explain the trade-offs both must consider when building applications.
Managing application state is a hard problem. You need to coordinate between multiple backends, web workers, and UI components. Patterns like Redux and Flux are designed to address this problem by making this coordination more explicit. In this article, we will learn how to implement a similar pattern in just a few lines of code using RxJS. Then we will learn how we can use this pattern to implement a simple Angular 2 application.
Zones are an execution context for asynchronous operations. They turn out to be really useful for things like error handling and profiling. In this article we’d like to dive a bit deeper into how zones work.
In this post we are going to see how an Angular 2 component library can be built and then consumed.
The author of this post, Mike Ryan, recently got the opportunity to help build a web app using Angular 2. He delves into his experiences building with the framework, good and bad.
In this blog post Developer Advocate for IBM, Raymond Camden, gives us his experiences in his first venture with Angular 2. Read on to find out what he liked and what he wasn't so crazy about in Angular 2.