5 Tips Before Deploying your Angular Apps to Production

So you’ve finally finished developing your Angular app 🙌. You’ve used the latest techniques, followed all the best-practices, neatly added unit tests to obtain 100% code coverage. All that’s left is running ng build —-prod and publish the /dist folder, right? Here are 5 tips to polish your Angular application before shipping it to production.

Tip #1: Browser Support

You’ve probably already clicked through your app in various different browsers to check if everything is working as expected. Luckily the majority of today’s modern browsers are all aligning with the new Web Standards. Furthermore they are mostly evergreen browsers, meaning they silently update in the background without prompting the user. In short: your app will likely work the same for most users, as wasn’t the case many years ago, but there still are some caveats.

The first thing you should ask yourself is: “who will use my app?”. Distributing your app to be publicly accessible to anyone (eg: an online platform to buy movie tickets) is different from distributing it to the intranet of a corporate where users all have IE11 installed on their machines.

Angular supports IE9+, and latest versions of Chrome, Safari, Firefox, Edge, iOS and Android, but not everything is supported by default.