Why routing is needed for SPAs in Angular - Visual Breakdown

Concept Flow - Why routing is needed for SPAs

User clicks link

↓

SPA intercepts click

↓

Routing logic checks URL

↓

Load matching component

↓

Update view without page reload

↓

User sees new content instantly

This flow shows how SPA routing intercepts user clicks, decides which component to show, and updates the view without reloading the whole page.

Execution Sample

Angular

import { Component } from '@angular/core';
import { RouterModule, Routes } from '@angular/router';

import { HomeComponent } from './home.component';
import { AboutComponent } from './about.component';

const routes: Routes = [
  { path: 'home', component: HomeComponent },
  { path: 'about', component: AboutComponent }
];

Defines routes so SPA knows which component to show for each URL path.

Execution Table

Step	User Action	Routing Check	Component Loaded	Page Reload?
1	Clicks 'home' link	URL '/home' matches route	HomeComponent	No
2	Clicks 'about' link	URL '/about' matches route	AboutComponent	No
3	Clicks browser refresh	Full page reload	App reloads	Yes
4	Clicks unknown link	No matching route	Show 404 or redirect	No

💡 Routing stops when no matching route is found or user refreshes page causing full reload.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
currentUrl	''	'/home'	'/about'	Browser reload	'/unknown'
loadedComponent	null	HomeComponent	AboutComponent	App reload	404Component

Key Moments - 3 Insights

Why doesn't the SPA reload the whole page when clicking links?

Because routing intercepts clicks and loads components dynamically without full page reload, as shown in execution_table steps 1 and 2.

What happens if the user refreshes the browser?

The browser performs a full page reload, reloading the entire app, as shown in execution_table step 3.

How does the SPA handle unknown URLs?

It shows a 404 component or redirects, without reloading the page, as shown in execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what component loads when the user clicks the 'about' link?

A AboutComponent

B HomeComponent

C 404Component

D No component

💡 Hint

Check row 2 under 'Component Loaded' in the execution_table.

At which step does the page reload fully?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look for 'Page Reload?' column in execution_table.

If the user clicks a link with no matching route, what happens?

A Loads HomeComponent

B Full page reload

C Shows 404 or redirects

D Does nothing

💡 Hint

See execution_table step 4 under 'Component Loaded'.

Concept Snapshot

Routing in SPAs lets the app change views without reloading the page.
It listens to URL changes and loads components dynamically.
This makes navigation faster and smoother.
Without routing, every link click reloads the whole page.
Routing also handles unknown URLs gracefully.
Angular uses RouterModule to define routes.

Full Transcript

Routing is needed in Single Page Applications (SPAs) to let users navigate between different views without reloading the entire page. When a user clicks a link, the SPA intercepts the click and checks the URL against defined routes. It then loads the matching component dynamically and updates the view instantly. This makes the app feel fast and smooth. If the user refreshes the browser, the whole app reloads. If the URL does not match any route, the SPA can show a 404 page or redirect. Angular uses RouterModule to set up these routes and manage navigation inside the SPA.

Practice

1. Why do Single Page Applications (SPAs) like Angular apps need routing?

easy

A. To disable navigation between different parts of the app

B. To change views without reloading the whole page

C. To make the app slower by adding extra steps

D. To reload the entire website every time a link is clicked

Solution

1. Step 1: Understand SPA behavior

   SPAs load a single HTML page and dynamically update content without full reloads.

2. Step 2: Role of routing in SPAs

   Routing allows changing views or components based on URL without reloading the entire page, making navigation smooth.

3. Final Answer:

   To change views without reloading the whole page -> Option B

4. Quick Check:

   Routing enables smooth view changes = D [OK]

Hint: Routing lets SPAs switch views without full page reloads [OK]

Common Mistakes:

• Thinking SPAs reload the whole page on navigation
• Believing routing slows down the app
• Confusing routing with disabling navigation

2. Which of the following is the correct way to define a route in Angular?

easy

A. { link: 'home', page: HomeComponent }

B. { url: 'home', view: HomeComponent }

C. { route: 'home', element: HomeComponent }

D. { path: 'home', component: HomeComponent }

Solution

1. Step 1: Recall Angular route syntax

   Angular routes use objects with path and component keys.

2. Step 2: Match correct keys

   Only { path: 'home', component: HomeComponent } uses path and component correctly.

3. Final Answer:

   { path: 'home', component: HomeComponent } -> Option D

4. Quick Check:

   Angular routes use path and component keys = A [OK]

Hint: Angular routes use 'path' and 'component' keys [OK]

Common Mistakes:

• Using wrong keys like url or route instead of path
• Confusing component with element or view
• Mixing route object structure with HTML attributes

3. Given this Angular route configuration:

const routes = [
  { path: '', component: HomeComponent },
  { path: 'about', component: AboutComponent }
];

What component will display when the URL is /about?

medium

A. HomeComponent

B. No component, shows blank page

C. AboutComponent

D. Error page component

Solution

1. Step 1: Match URL to route path

   The URL /about matches the route with path: 'about'.

2. Step 2: Identify component for matched route

   The route with path: 'about' uses AboutComponent.

3. Final Answer:

   AboutComponent -> Option C

4. Quick Check:

   URL '/about' loads AboutComponent = C [OK]

Hint: URL path matches route path to load component [OK]

Common Mistakes:

• Assuming empty path matches '/about'
• Thinking HomeComponent loads for all URLs
• Expecting error or blank page without reason

4. What is wrong with this Angular routing code?

const routes = [
  { path: 'home', component: HomeComponent },
  { path: 'about', component: AboutComponent }
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule]
})
export class AppRoutingModule {}

The app does not navigate to the About page when clicking the link <a routerLink='/about'>About</a>.

medium

A. RouterModule is not imported in the main app module

B. The routes array is missing a default route for '' path

C. routerLink should be written as routerlink (lowercase L)

D. The component names are incorrect

Solution

1. Step 1: Check routing module setup

   The routing module is defined correctly but must be imported in the main app module to work.

2. Step 2: Identify missing import

   If AppRoutingModule is not imported in AppModule, routing won't activate, causing navigation failure.

3. Final Answer:

   RouterModule is not imported in the main app module -> Option A

4. Quick Check:

   Routing module must be imported in app module = B [OK]

Hint: Always import routing module in main app module [OK]

Common Mistakes:

• Thinking routerLink attribute is case-sensitive
• Assuming default route is required for all navigation
• Blaming component names without error evidence

5. You want your Angular SPA to show a 'Not Found' page when users enter an unknown URL. How should you add this behavior using routing?

hard

A. Add a route with path: '**' and a NotFoundComponent

B. Add a route with path: '' and a NotFoundComponent

C. Add a route with path: '404' and redirect all unknown URLs manually

D. No routing needed; Angular shows a default error page automatically

Solution

1. Step 1: Understand wildcard route usage

   Angular uses path: '**' as a wildcard to catch all unmatched URLs.

2. Step 2: Assign NotFoundComponent to wildcard route

   Defining { path: '**', component: NotFoundComponent } shows the Not Found page for unknown URLs.

3. Final Answer:

   Add a route with path: '**' and a NotFoundComponent -> Option A

4. Quick Check:

   Wildcard '**' route handles unknown URLs = A [OK]

Hint: Use '**' path to catch unknown URLs for Not Found page [OK]

Common Mistakes:

• Using empty path '' for Not Found page
• Manually redirecting unknown URLs instead of wildcard
• Expecting Angular to handle unknown URLs without setup