Multiple Components in React – Structure, Instantiation, and Hierarchical Growth

In React, each component represents a self-contained unit of logic and UI. As your application grows, components should be split into smaller parts to maintain clarity and scalability. This article explains how to extract components, build a component hierarchy, and instantiate components in JSX — with practical examples and analogies to JavaScript classes.

componentinstantiationhierarchyrefactoring

~2 min read · Updated Oct 21, 2025

Introduction


Components are the foundation of every React application. Each component handles a specific part of the UI or logic. As your project grows, it's important to split components into smaller, manageable units to keep the code maintainable and scalable.


Extracting Components


Initially, everything may live inside the App component. But instead of making it larger, we can extract parts like the item list or search form into separate components:


List Component:


function List() {
  return (
    
    {list.map(item => (
  • {item.title} {item.author} {item.num_comments} {item.points}
  • ))}
); }

Search Component:


function Search() {
  return (
    
); }

Component Hierarchy


React components form a tree structure. The App component is the root, and List and Search are its children. If we extract an Item component from List, the hierarchy looks like this:


  • App: Root component
  • List and Search: Children of App
  • Item: Child of List

Components that don’t render other components are called leaf components.


Component Instantiation


Declaring a component is like defining a class. Using it in JSX is like creating an instance:


function List() { ... }

function App() {
  return (
    
); }

You can create multiple instances of a component as long as it’s declared. This is similar to class instantiation in JavaScript, though technically different.


Best Practices


  • Each component should have a clear purpose.
  • Extract components when they grow too large or have distinct functionality.
  • Organize components into separate files for better structure and readability.

Conclusion


As React projects grow, organizing components into a clear hierarchy and extracting reusable units becomes essential. Component instantiation allows you to reuse logic and UI efficiently, while refactoring keeps your codebase clean and scalable.


Written & researched by Dr. Shahin Siami

Related Articles

Forms in React – Submitting Data with onSubmit and Action in Search Forms

react-forms-Forms are essential in modern applications. This article walks through building a search form in React using input and button elements. First, we use the onSubmit attribute to manage form submission, then introduce the action attribute to align with native HTML behavior. This structure improves accessibility, readability, and prepares the app for future React updates.submit-search-with-onsubmit-and-action

Continue

Third-Party Libraries in React – Using Axios and Async/Await for Data Fetching

This article explores how to replace the native fetch API with the more stable and feature-rich Axios library for data fetching in React. It also demonstrates how to refactor promise-based code using async/await and try/catch blocks for improved readability and error handling. These techniques enhance compatibility with older browsers, improve testability, and simplify asynchronous logic.

Continue

Explicit Data Fetching in React – Controlling API Requests with a Confirmation Button

In the initial implementation, every keystroke in the search field triggered a new API request. This article demonstrates how to shift to explicit data fetching in React, where data is only fetched when the user clicks a confirmation button. By separating the searchTerm and url states, and using useCallback and useEffect, we gain full control over when API requests are sent.

Continue

Impossible States in React – Predictable State Management with useReducer

Using multiple useState hooks to manage related states like data, loading, and error can lead to impossible states — combinations that should never occur in a well-designed UI. This article shows how to consolidate related states into a single useReducer hook, enabling predictable transitions and eliminating bugs like simultaneous loading and error indicators. By structuring state as a complex object and dispatching clearly defined actions, we gain control and clarity in asynchronous data flows.

Continue

Advanced State Management in React – Using useReducer for Complex Transitions

While useState is ideal for simple state updates, React’s useReducer hook offers a more scalable solution for managing complex state transitions. This article demonstrates how to migrate story-related state from useState to useReducer, handle multiple actions like setting and removing stories, and refactor reducer logic for clarity. It’s a foundational step toward building robust, declarative state logic in React applications.

Continue

Conditional Rendering in React – Displaying Loading and Error States for Asynchronous Data

Conditional rendering in React is a powerful tool for controlling what appears in the UI based on different states. This article explains how to show a “Loading…” message while asynchronous data is being fetched, and how to display an error message if the request fails. Using useState and useEffect, we manage isLoading and isError flags, and render content dynamically using ternary and logical operators.

Continue