If you've recently made the switch to using Strict Mode for Angular, good job, you're on your way to writing better code and governing a more maintainable codebase! However, your team may encounter new TypeScript "errors" they haven't seen before, like "Property 'myClassMember' has no initializer and is not definitely assigned in the constructor.ts". To find out more about this error and how to resolve it using the Non-null Assertion Operator, check out my post on dev.to here: https://dev.to/bitovi/non-null-assertion-operator-in-angular-g5l

Psst, hey you! Are you looking for a place to grow your Angular skills by working on interesting projects with fabulous teammates? 

At Bitovi we’re expert developer consultants that care about our craft and care about helping our customers achieve success in their software products. We invest ourselves fully in client success and make sure we bring the development knowledge & consulting skills they need to achieve their goals.

Scully is still a new and emerging technology, allowing developers to convert their Angular apps to use JAMstack methodology. Learning how to improve Angular application performance by pre-rendering pages with Scully can be hard if you don't understand how Scully works or how to debug Scully errors (or lack of errors).  

When considering how to improve Angular performance, there are many things we can borrow from the JAMstack approach. One of these, caching API calls, can be a real performance booster AND save money by limiting server requests to fetch redundant information.

There are a number of ways to improve Angular application performance, but one sure-fire way to see page load times improve immediately is to move toward JAMstack architecture, and using Scully is a great way to do this.

In the 2020 economy of competing web applications and SaaS products, an application's performance can be the difference between a customer gained and a customer lost. Angular is a fantastic framework for creating scalable web applications.  However, it is just as susceptible to performance issues as any other technology if the development team isn't experienced in Angular best practices, optimization, and performance consideration.

While there are many factors that impact Angular application performance,  consider one common result of poor performance; page load time. The longer a web application takes to load, the more likely a user is to leave the site without taking an action that may lead to a sale. 

Google doesn’t disclose its ranking algorithm or list a concrete goal for performance, so a company should ensure their application performs better than their competitors’  in order to be successful.

Conversion Impact