React guides for developers and teams in Estonia
Current, practical explanations of modern React: how to learn it, when to choose it, how Next.js and Server Components fit in, and how to hire people who know it.
fig. 1Stock footage: a diagram being drawn in a notebook.
three working assumptions
What these pages assume
a
Modern React, not legacy habits
The guides assume React 19, function components, Server Components and a framework or Vite as the starting point, not patterns from older tutorials.
b
For developers and decision makers
Some topics are for people writing code. Others help founders and team leads choose a stack and hire for it.
c
Accurate over exhaustive
Where an interface is still changing between framework versions, the guides explain the concept and point to the official documentation for specifics.
One tree, five things React does to it
1 of 5: Initial render
A render is a tree of function calls
React calls the root component, then the components it returns, and so on down the tree.
React calls the root component. It returns elements, React calls the components those name, and so on down until it knows what the whole screen should be.
2 of 5: An event
A click reaches the component that owns the state
AddButton has no state. Its click handler calls a setter that Cart passed down as a prop.
AddButton has no state of its own. Its click handler calls a setter that Cart passed down as a prop. Setting state does not change the screen yet; it asks React to render again.
3 of 5: Re-render
React re-renders from the owner down
Cart is called again and, by default, so are its children. Nothing above or beside it re-renders.
Cart is called again, and by default so are its children. App, Header and Details are not touched. React then commits only the DOM nodes whose output changed. memo or the React Compiler can skip a child whose props did not change.
Where state should live4 of 5: The boundary
“use client” splits the tree in two
Files marked “use client”, and what they import, ship to the browser. The rest render on the server only.
Files marked “use client”, and everything they import, are sent to the browser as JavaScript. The rest are Server Components: they render on the server only and their code is never shipped.
Server Components explained5 of 5: Hydration
On first load the browser gets HTML, then React hydrates
The first response is HTML. React then renders the Client Components in the browser and attaches their handlers.
The first response is HTML for the whole page, Client Components included. React then renders the Client Components in the browser and attaches their event handlers to that HTML. Server Components do not hydrate: they have nothing to run there.
Next.js and the App Router
Cyan means one thing here: rendering now.
a sequence, so numbered
The order to learn it in
Six stages, numbered because the order matters. Each one ends with something to build before you move on.
1
JavaScript before React
React is JavaScript. Functions, arrays and objects, modules and async code come first, with working HTML and CSS.
Open this stage in the guide2
The core: components, props, state
Work through react.dev in a Vite project until rendering lists, handling events and lifting state up feel obvious.
Open this stage in the guide3
The other hooks, and when not to use them
Effects, refs, context, reducers and custom hooks. Then the React 19 additions: Actions, useOptimistic and use.
Open this stage in the guide4
TypeScript
Type props, state, event handlers and API data. Convert an earlier project; it teaches more than a separate course.
Open this stage in the guide5
A framework, data and state
Next.js with the App Router: routes, Server and Client Components, Server Functions. Then decide where each piece of state belongs.
Open this stage in the guide6
Test it, ship it, show it
Component tests, one end-to-end test of the main flow, and one real application taken all the way to a public URL.
Open this stage in the guide
try it
Drag the state. See what re-renders.
AddButton has to change the cart and Cart has to show it. Put the state on a component and React re-renders that component and everything under it.
Drag this onto a component, or click a component.
reads the cart
sets the cart
Nothing owns the state yet.
Default behaviour, without memoisation. memo or the React Compiler can skip a child whose props did not change. When the common parent is far away, context or a small store avoids passing props through every level.
seven topics, three branches
Topics
All 7 topics






Longer pieces. Each opens with the direct answer.
Guides
- How Much Does a React Developer Cost in Estonia?The cost of a React developer in Estonia depends on seniority and on the hiring model: employee, freelancer or agency. See what makes up the full cost of each.4 min read
- How to Learn React in 2026: A Step-by-Step Path for Developers in EstoniaA step-by-step path for learning React in 2026: JavaScript first, then components and state, hooks, TypeScript, a framework such as Next.js, and testing.4 min read
- React Server Components Explained: A Guide for Developers in EstoniaReact Server Components render on the server and send no component code to the browser. Learn how they differ from Client Components and when to use each one.4 min read
- React vs Vue vs Svelte vs Angular: How Teams in Estonia Can Choose in 2026Compare React, Vue, Svelte and Angular on ecosystem, learning curve, structure, hiring and mobile, and choose the frontend framework that fits your team.4 min read
How long is your path?
Three questions: what you know, what you want, how many hours a week you have. The planner returns an ordered list of stages with something to build at each one.
- 9
- stages
- 48
- weeks, roughly
example: starting from zero, 8 hours a week
Stock footage.
from our network
For teams and freelancers: services from our network
These guides are published by the team behind four services. If you build with React for a living, or are about to pay someone who does, these are the ones that fit.
answers first
Questions people ask
Is React still worth learning in 2026?
Yes. React remains one of the most widely used tools for building web interfaces, with a large ecosystem, an active job market and continued development, including React 19 and the React Compiler. The skills also carry over to mobile development with React Native. The fundamentals you learn, such as components and state, apply in other frameworks too.
Do I need Next.js to use React?
No, but you need some build setup. The React team recommends starting new applications with a framework such as Next.js or React Router, which provide routing, data loading and server rendering. For a client-only application or for learning, a build tool such as Vite is a good choice. Create React App is deprecated and should not be used for new projects.
What is new in React 19?
React 19 added Actions for handling form submissions and async updates, with hooks such as useActionState and useOptimistic, and a new use API for reading promises and context during render. It made Server Components and Server Functions stable, allowed ref to be passed as an ordinary prop to function components, and added built-in support for document metadata tags.
What is the difference between a Server Component and a Client Component?
A Server Component renders only on the server and sends its output, not its code, to the browser. It can fetch data directly but cannot use state or event handlers. A Client Component is marked with the use client directive, is included in the browser bundle and can be interactive. Client Components are usually still pre-rendered to HTML on the server.
Should a new project use React or another framework?
Choose React when you value a large ecosystem, a wide hiring pool or a shared approach with a React Native mobile app. Vue, Svelte and Angular are all capable alternatives, and each suits certain teams better. The strongest factor is usually what your current and future developers already know, since productivity depends more on experience than on the framework.
Do I need Redux for state management?
Usually not at the start. Component state, the URL and a server-data library or framework cover most needs, and Context handles simple shared values. Add a store when several distant parts of the interface must share and update the same client state. Redux Toolkit remains a solid choice for large applications, and lighter libraries such as Zustand suit smaller ones.







