Things to consider while designing Angular application

If you are a developer of web applications, its not possible that you haven’t heard about the Angular framework. While this post is being written, its 7.2.4 version has been published which was first published (Angular 2) in September 2016. If you have worked or even played with it, you must have noticed that it’s simply amazing that all the necessary bits and pieces – building blocks – are clubbed into a single framework – which makes it very developer friendly.

To fully utilise and envisage the features of Angular, there are few things we must consider while designing the UI project. If developers of your project have not structured and designed the code base properly, your team won’t be able to reap the benefits of using this great framework. Moreover, you’ll see some of the symptoms near to the end of your release cycle if you don’t observe them properly – which will make it even more challenging to be fixed.

I have kept some points apart so that others can consider it while starting with their Angular project.

1. Utilise lazy loaded modules and routing
2. Let your UX team know how you can add value to your product
3. Create separate chunk for 3rd party npm packages
4. Don’t use hard coded values – instead encrypt them from server and decrypt at client. i.e. license keys
5. Use nrwl workspace while working with multiple UI applications
6. Never access DOM elements the jQuery way
7. Keep checking the performance with Augury
8. Unsubscribe on ngDestory or whenever you are done with the observable
9. Last but not the least, always follow Angular style guide

I will be delineating all the necessary points in details; let me know if you particularly would like to know more about any point.

*Views are my personal