Single Page Application concept in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Single Page Application (SPA)?

A Single Page Application is a web app that loads a single HTML page and updates content dynamically without reloading the whole page. It feels fast and smooth like a desktop app.

beginner

How does a SPA improve user experience compared to traditional websites?

SPAs update parts of the page instantly without full reloads, so users see changes faster and navigation feels seamless, like switching views in a mobile app.

intermediate

Which React feature helps build SPAs by managing page views without reloading?

React Router is a library that lets you handle navigation inside a SPA by changing views and URLs without reloading the page.

beginner

Why do SPAs often use APIs to get data?

SPAs get data from APIs so they can update parts of the page dynamically without reloading. This keeps the app fast and responsive.

intermediate

Name one challenge of SPAs and how it can be addressed.

One challenge is SEO because content loads dynamically. This can be addressed by server-side rendering or pre-rendering to help search engines see the content.

What does a Single Page Application primarily avoid?

A Using JavaScript for interactivity

B Reloading the entire webpage on navigation

C Loading any data from servers

D Changing the URL in the browser

SPAs avoid full page reloads to provide a smoother user experience.

Which React tool is commonly used to manage navigation in SPAs?

A React Router

B Redux

C Axios

D React Hooks

React Router helps manage page views and URLs without reloading the page.

How do SPAs usually get new data to show on the page?

A By using CSS only

B By reloading the whole page

C By fetching from APIs asynchronously

D By embedding all data in the HTML

SPAs fetch data from APIs to update content dynamically without reloading.

What is a common SEO challenge with SPAs?

A SPAs do not support images

B SPAs cannot use URLs

C SPAs always reload pages

D Search engines may not see dynamically loaded content

Because SPAs load content dynamically, search engines might miss some content unless special techniques are used.

Which of these is NOT a benefit of SPAs?

A Better SEO by default

B Smooth user experience like apps

C Faster navigation without full reloads

D Dynamic content updates

SPAs often need extra work for SEO; it is not better by default.

Explain in your own words what a Single Page Application is and how it works.

Think about how apps on your phone switch screens without reloading.

Describe one main advantage and one challenge of using SPAs.

Consider what users like and what search engines might struggle with.

Practice

1. What is the main advantage of a Single Page Application (SPA) compared to traditional multi-page websites?

easy

A. It uses only server-side rendering without JavaScript.

B. It loads the page once and updates content dynamically without full reloads.

C. It requires a new page load for every user action.

D. It does not support navigation between different views.

Solution

1. Step 1: Understand SPA behavior

   SPAs load a single HTML page and dynamically update content without reloading the entire page.

2. Step 2: Compare with traditional websites

   Traditional sites reload the whole page on navigation, causing slower user experience.

3. Final Answer:

   It loads the page once and updates content dynamically without full reloads. -> Option B

4. Quick Check:

   SPA = dynamic content update without reload [OK]

Hint: SPAs avoid full page reloads for faster user experience [OK]

Common Mistakes:

• Thinking SPAs reload pages on every action
• Confusing SPAs with server-only rendering
• Believing SPAs don't support navigation

2. Which React library is commonly used to manage navigation and URL paths in a Single Page Application?

easy

A. Styled Components

B. Redux

C. Axios

D. React Router

Solution

1. Step 1: Identify navigation management in React

   React Router is designed to handle routing and URL paths in SPAs.

2. Step 2: Differentiate other libraries

   Redux manages state, Axios handles HTTP requests, Styled Components manage styling.

3. Final Answer:

   React Router -> Option D

4. Quick Check:

   Routing in React SPA = React Router [OK]

Hint: React Router controls SPA navigation and URLs [OK]

Common Mistakes:

• Confusing Redux with routing
• Thinking Axios manages navigation
• Assuming styling libraries handle routing

3. Given this React SPA code snippet using React Router:

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path='/' element=<Home /> />
        <Route path='/about' element=<About /> />
      </Routes>
    </BrowserRouter>
  );
}

What happens when the user navigates to /about URL?

medium

A. Nothing happens because routes are not defined correctly.

B. The browser reloads the entire page and shows About component.

C. The About component renders without a full page reload.

D. The Home component renders instead of About.

Solution

1. Step 1: Analyze React Router setup

   The Route with path '/about' renders the About component inside BrowserRouter.

2. Step 2: Understand SPA navigation

   React Router updates the view without reloading the whole page when navigating to '/about'.

3. Final Answer:

   The About component renders without a full page reload. -> Option C

4. Quick Check:

   React Router navigation = no full reload [OK]

Hint: React Router changes views without reloading page [OK]

Common Mistakes:

• Assuming full page reload on route change
• Thinking routes are not matched correctly
• Confusing Home and About components

4. Identify the error in this React SPA routing code:

import { BrowserRouter, Routes, Route } from 'react-router-dom';

function App() {
  return (
    <BrowserRouter>
      <Routes>
        <Route path='/' component={Home} />
        <Route path='/profile' element=<Profile /> />
      </Routes>
    </BrowserRouter>
  );
}

medium

A. The first Route uses 'component' prop instead of 'element'.

B. The BrowserRouter is missing a closing tag.

C. Routes should be replaced with Switch.

D. Profile component is not imported.

Solution

1. Step 1: Check Route props

   React Router v6 uses 'element' prop with JSX, not 'component'.

2. Step 2: Verify other code parts

   BrowserRouter is properly closed, Routes is correct in v6, and Profile import is not shown but not necessarily an error here.

3. Final Answer:

   The first Route uses 'component' prop instead of 'element'. -> Option A

4. Quick Check:

   React Router v6 Route uses element prop [OK]

Hint: Use 'element' prop with JSX in React Router v6 [OK]

Common Mistakes:

• Using 'component' prop from older React Router versions
• Confusing Routes with Switch in v6
• Assuming missing closing tags without checking

5. You want to build a React SPA that shows a loading spinner while fetching user data on route change. Which approach best fits SPA principles?

hard

A. Use React Router for routes and show a spinner component while fetching data asynchronously in the route component.

B. Reload the entire page on each route change to fetch fresh data.

C. Fetch all user data once on app load and never update it.

D. Use multiple HTML pages and link between them for each user view.

Solution

1. Step 1: Understand SPA data fetching

   SPAs fetch data asynchronously and update views without full reloads.

2. Step 2: Implement loading state in route components

   Showing a spinner while fetching data fits SPA dynamic update and user feedback.

3. Step 3: Eliminate non-SPA approaches

   Reloading pages or using multiple HTML pages breaks SPA flow; fetching once without updates is inflexible.

4. Final Answer:

   Use React Router for routes and show a spinner component while fetching data asynchronously in the route component. -> Option A

5. Quick Check:

   SPA + async data + spinner = Use React Router for routes and show a spinner component while fetching data asynchronously in the route component. [OK]

Hint: Show spinner during async fetch inside SPA route components [OK]

Common Mistakes:

• Reloading pages instead of dynamic updates
• Not showing loading feedback during fetch
• Ignoring SPA dynamic data needs