ENATIV Logo
ENATIV
Back
© 2026 ENATIV
ProjectsServicesKnowledge hubContact
contact@enativ.pl
  1. Knowledge hub
  2. ›
  3. Frontend
  4. ›
  5. React

React

A library for component-based interfaces, with state, Server Components and a compiler.

FrontendUsing since 2016 · Featured project: Budzowska Fiutowski i Partnerzy

Category
Frontend
Using since
2016
Featured project
Budzowska Fiutowski i Partnerzy

In practice

For me React is the view layer: components, state and an interface that reacts to data. I use it in services with a dashboard, forms and a lot of data, for example Gaia Lens. Routing and page rendering I leave to the framework, which I cover in the entry on Next.js.

What is React?

React is a library for building interfaces out of components. A component takes data and returns a piece of the view, and when the data changes, React updates what the user sees. That split lets you assemble a large screen from small, reusable parts.

Data flows one way: from a parent component to its children, through props. State is data a component remembers between renders, and changing it refreshes the view. You pull reusable logic out into custom hooks. You describe the view in JSX, a syntax where markup sits next to JavaScript code.

Server Components render ahead of time, outside the browser, so they cannot use state. You add interactivity with Client Components. React Compiler is a build-time tool that optimizes the app on its own, without manual memoization.

Reach
Web and native interfaces
Split
Server and Client Components

How I work with React

I start with the split into components and with where state lives. The rest follows from those two decisions.

  1. Split into components

    I start with the screen drawn as small, reusable parts. Only then do I work out which data flows into them and which of them have to react to the visitor.

  2. Server and client

    I keep a component on the server while rendering data is enough. What reacts to the visitor becomes a Client Component, because only there is state needed.

  3. Heavy parts later

    Sections that weigh a lot I mount only when the visitor gets close to them. In ENATIV Portfolio the AI chat and the contact form load that way, and animations respect prefers-reduced-motion.

When it fits, and when it doesn't

React fits where an interface has state and reacts to data.

A good fit when

  • A dashboard or app with forms, tables and views that depend on the role.
  • An interface that shows a lot of data and has to stay smooth.
  • A site with animations and interactive sections, not only text.
  • A product that also has a mobile version in React Native, because the component model is the same.

Not a fit when

  • A site of plain text and images with no interaction at all.
  • A tiny script or widget for which the whole library would be dead weight.
  • A team where nobody knows JavaScript or TypeScript.

When you need a framework with routing and server rendering, I describe it in the entry on Next.js.

Frequently asked questions

React handles the interface: components and state. Next.js adds routing, server rendering and caching, and the two together make a whole application. On Gaia Lens the frontend moved to React 19, and the app was built on Next.js with server-side rendering.
It depends on the reason. On Gaia Lens the JavaScript codebase was getting hard to scale, so a full migration to TypeScript and React 19 made sense. When a site works and nobody develops it, a rewrite improves nothing. Then I check what actually hurts and start there.
React is a library for building interfaces, not a full framework. It does not dictate routing, data fetching or a folder structure, so you make those decisions yourself or leave them to a framework such as Next.js. In a small app that is freedom, and in a larger one the team has to agree on those rules up front. That is why React fits both a single widget and the view layer of a whole application, while the rest of the stack depends on the project.
The weight depends on what reaches the browser. Server Components are not sent to it, and heavy sections can be mounted later. In ENATIV Portfolio the chat and the form load only when you scroll near them, because their hydration was hurting the Lighthouse result.

On this page

  • In practice
  • What is React?
  • How I work with React
  • When it fits, and when it doesn't
  • Frequently asked questions

Related topics

  • React
  • Next.js
  • TypeScript
  • React Native
  • Core Web Vitals

Related services

  • Web ApplicationsModern, fast and scalable web applications using React and Next.js.
  • Landing PagesHigh-converting landing pages optimized for marketing campaigns.
  • Website RedesignRedesign and migration without losing your Google rankings - URL mapping, 301 redirects, and post-launch verification.
  • Performance OptimizationMeasured performance optimization - component-mount profiling and Core Web Vitals audits with a documented before/after result, not a vague promise.

Building an interface with a lot of state?

Send a list of views, roles and data sources. I will propose the split into components and the line between the server part and the client part.

Describe your projectSee Budzowska Fiutowski i Partnerzy