This article contains some timeless approaches to designing an application that fits any form-factor.
How can we create a web app that will look and feel amazing in any resolution? In this article, we will learn how to use traditional software architecture and design patterns to harness the power of the Angular platform to create a state-of-the-art web app that can be viewed in any device at any resolution.
The follow up article to Ben Lesh's "When to Unsubscribe". Michael lays out some rules to show when subscribing is appropriate within different aspects of the Angular ecosystem.
Recent developments at Google appear to have stalled the progress on the built -n i18n features. If you're interested in checking out an alternative to the default i18n and ngx-translate, you can check out the new kid on the block and give Transloco a try.
A couple of weeks ago I was bored 😀, so I decided that’s it time to take the bull by the horns and go ahead and create a robust library, chock-full of all the features I’d expect from such a library.
Builders in Angular 8 are an extremely powerful feature. They are vastly more simple than the old process of ejecting your webpack configuration. You should definitely understand the options available with the builders if you use web components and ngx-build-plus.
With Angular 8 release the CLI builders API were made public. and with builders being a public API, it opened a lot of possibilities for Angular lovers.
With CLI builders it has become easy to create and use your own builders without ejecting the webpack config. Even it is not possible to ng eject command anymore.
Are you using feature flags in your application? If you are, are you using them to prevent lazy loaded modules from even loading if the user isn't authorized to use the feature? This is a great walk-through on how to set up structural directives, guards, preloading strategies, and the APP_INITIALIZER to use feature flags in your apps.