Introducing the Angular Router

In traditional web applications, when we wanted to change from one view to another, we needed to request a new page from the server. The browser would create a URL for the view and send it to the server. The browser would then reload the page as soon as the client received a response. It was a process that resulted in round-trip delays and a bad user experience for our applications.