Context API, useContext & Global Application State

Master state management in modern React applications by sharing state globally across components without prop drilling.

1. The Prop Drilling Problem

In standard React, data flows downward through props from parent to child components.

When deeply nested components (e.g. 5 layers deep) need access to global state (such as the current authenticated user, active UI theme, or shopping cart), passing props through intermediate components that do not need them creates prop drilling.

React Context provides a way to pass data through the component tree without having to pass props down manually at every level.

2. Creating Context with createContext

Create a Context object and establish fallback default values:

⊞Code Example

import { createContext } from 'react';

// Create context with sensible default values

export const ThemeContext = createContext({

theme: 'dark',

toggleTheme: () => {}

});

3. The Context Provider Pattern

Wrap your component tree in a custom Provider component that owns and manages the state:

⊞Code Example

import React, { useState } from 'react';

import { ThemeContext } from './ThemeContext';

export function ThemeProvider({ children }) {

const [theme, setTheme] = useState('dark');

const toggleTheme = () => {

setTheme((prevTheme) => (prevTheme === 'dark' ? 'light' : 'dark'));

};

return (

<ThemeContext.Provider value={{ theme, toggleTheme }}>

{children}

</div>

</ThemeContext.Provider>

);

}

4. Consuming State with useContext

Create a custom consumer hook to safely access the context anywhere in your application:

⊞Code Example

import { useContext } from 'react';

import { ThemeContext } from './ThemeContext';

export function useTheme() {

const context = useContext(ThemeContext);

if (!context) {

throw new Error('useTheme must be used within a ThemeProvider');

}

return context;

}

5. Complete Global State Implementation

Here is how consumer components cleanly toggle and read global state:

⊞Code Example

import React from 'react';

import { useTheme } from './ThemeContext';

export function HeaderNav() {

const { theme, toggleTheme } = useTheme();

return (

<h1 className="text-xl font-bold">Nextsem Academy</h1>

<button

onClick={toggleTheme}

className="px-4 py-2 bg-[#04AA6D] hover:bg-[#039861] text-white font-bold rounded-lg transition-colors"

Current Theme: {theme.toUpperCase()}

</button>

</header>

);

}

6. Context Performance Best Practices

Split Independent Contexts: Avoid putting all state into a single giant context object. Keep authentication, UI theme, and notification state in separate providers.

Separate State and Dispatch: If a component only needs to trigger an action (e.g. dispatch a toggle), provide a separate context for action handlers so state updates do not re-render that component.

Context API, useContext & Global Application State

Master state management in modern React applications by sharing state globally across components without prop drilling.

1. The Prop Drilling Problem

In standard React, data flows downward through props from parent to child components.

React Context provides a way to pass data through the component tree without having to pass props down manually at every level.

2. Creating Context with createContext

Create a Context object and establish fallback default values:

⊞Code Example

import { createContext } from 'react';

// Create context with sensible default values

export const ThemeContext = createContext({

theme: 'dark',

toggleTheme: () => {}

});

3. The Context Provider Pattern

Wrap your component tree in a custom Provider component that owns and manages the state:

⊞Code Example

import React, { useState } from 'react';

import { ThemeContext } from './ThemeContext';

export function ThemeProvider({ children }) {

const [theme, setTheme] = useState('dark');

const toggleTheme = () => {

setTheme((prevTheme) => (prevTheme === 'dark' ? 'light' : 'dark'));

};

return (

<ThemeContext.Provider value={{ theme, toggleTheme }}>

{children}

</div>

</ThemeContext.Provider>

);

}

4. Consuming State with useContext

Create a custom consumer hook to safely access the context anywhere in your application:

⊞Code Example

import { useContext } from 'react';

import { ThemeContext } from './ThemeContext';

export function useTheme() {

const context = useContext(ThemeContext);

if (!context) {

throw new Error('useTheme must be used within a ThemeProvider');

}

return context;

}

5. Complete Global State Implementation

Here is how consumer components cleanly toggle and read global state:

⊞Code Example

import React from 'react';

import { useTheme } from './ThemeContext';

export function HeaderNav() {

const { theme, toggleTheme } = useTheme();

return (

<h1 className="text-xl font-bold">Nextsem Academy</h1>

<button

onClick={toggleTheme}

className="px-4 py-2 bg-[#04AA6D] hover:bg-[#039861] text-white font-bold rounded-lg transition-colors"

Current Theme: {theme.toUpperCase()}

</button>

</header>

);

}

6. Context Performance Best Practices

Split Independent Contexts: Avoid putting all state into a single giant context object. Keep authentication, UI theme, and notification state in separate providers.

Context API, useContext & Global Application State

1. The Prop Drilling Problem

2. Creating Context with createContext

3. The Context Provider Pattern

4. Consuming State with useContext

5. Complete Global State Implementation

6. Context Performance Best Practices

Student Learning Dashboard

Guest Student

Computer Competency Test (CBT)100 MCQs

Practical Lesson UpdatesCoding Labs Only

Professional & Social IntegrationsPortfolio & Network

Context API, useContext & Global Application State

1. The Prop Drilling Problem

2. Creating Context with createContext

3. The Context Provider Pattern

4. Consuming State with useContext

5. Complete Global State Implementation

6. Context Performance Best Practices