Having an AngularJS app in 2018 probably means one of two things: either the app has been abandoned and isn’t really used or you’ve been thinking about migrating to another framework, but the time and costs that would entail have been prohibitive enough to have prevented you from drafting a roadmap for moving forward.
We recently had new clients come to us. They had an application, written in AngularJS, with hard performance issues and heard that we could help them improve it without rewriting half (or more) of the code. I'd like to share the story and solution of one of the problems we encountered. I learned a lot and hope that this post will help people who are looking for similar knowledge. By the way, I encourage you, dear reader, to dig into Angular (or any other framework) internals yourself - I found it fun and inspiring!
As a web developer, there inevitably comes a time when we have to add responsiveness to an application. If you use Angular at your work, I've found some solutions that may help you deliver beautiful experience for multiple devices. Some of them are pretty basic, but they are still good practices you should follow.
PS. Every example below is written in CoffeeScript, SASS or SLIM.
During my recreational reading of Angular.js documentation I made a handful of notes describing some little-known, yet useful directives. Bon appétit.
At Monterail, we’ve fallen in love with Angular.js. It focuses on data and state instead of how your
DOM should look like and where all those
ids and classnames are. Unfortunately, there are still fields with dragons which we need to discover and learn how to deal with. Like the server-side form validation.