React Day Berlin

Attendees, exhibitors & solutions

Who this event is for

Industry trends

Key trends shaping this market and its wider industry.

Arrival airports

Choose from the following airports, with convenient access to the event and venue.

Hotel tiers

A range of accommodation options near the venue and across key areas.

Local transport

Get around the city with these convenient transport options.

Frequently asked

Glossary

1

React

The open-source JavaScript library for building user interfaces from composable components, maintained by Meta and the community. Most React Day Berlin talks, workshops and hallway debates circle around how React renders, ships and hydrates UI in production apps.

2

React Server Components (RSC)

A React architecture where some components render only on the server and stream serialized output to the client, so their dependencies never enter the browser bundle. A recurring theme in modern React app design and a common workshop topic at React-focused conferences.

3

Server Actions

Async functions marked for server execution that can be called directly from client components, letting forms and mutations run without hand-written API endpoints. Frequently paired with RSC in full-stack React frameworks.

4

Hooks

Functions such as useState, useEffect and useMemo that let function components hold state and side effects. Expect hook-level detail (dependency arrays, custom hooks, useTransition) in intermediate and advanced sessions.

5

Suspense and streaming

React's mechanism for showing fallbacks while data or code loads, and for streaming HTML progressively from the server. Central to perceived-performance discussions at React conferences.

6

Hydration

The client-side step that attaches event handlers and state to server-rendered HTML. Hydration mismatches and partial or selective hydration are frequent debugging stories in React talks.

7

Concurrent Rendering

React's scheduling model that lets renders be interrupted and prioritized so urgent updates (typing, clicks) are not blocked by heavy work. Underpins transitions and modern suspense-based data flows.

8

React Compiler

The build-time optimizing compiler that automatically memoizes components and hooks. A practical topic for teams auditing re-render performance and removing manual useMemo/useCallback noise.

9

Signals

Fine-grained reactive primitives adopted by several JavaScript frameworks and discussed as an alternative or complement to React's re-render model. Usually debated in conference talks on state and reactivity.

10

TypeScript

The typed superset of JavaScript that most large React codebases now use. Conference workshops often cover typing component props, generics in hooks and safe API boundaries.

11

Next.js

A React framework providing routing, server rendering, RSC and deployment conventions. One of several frameworks attendees compare when choosing an application architecture.

12

Remix and React Router

Routing and data-loading approaches built around web standards, nested routes and progressive enhancement. Often contrasted with RSC-centric frameworks in architecture sessions.

13

Design system

A shared library of tokens, components and usage rules used across products. Conference talks typically cover theming, accessibility contracts and versioning a component library for multiple teams.

14

Bundle size and code splitting

The practice of measuring and reducing the JavaScript shipped to the browser, using dynamic imports and route-level splits. A staple of React performance sessions.

15

Core Web Vitals

Google's user-experience metrics (LCP, INP, CLS) used to judge real-world page performance. Frequently the scoreboard in React performance case studies.

16

Accessibility (a11y)

Building interfaces usable with screen readers and keyboards. React-specific concerns include focus management in modals, semantic component APIs and testing with axe tooling.

17

Hallway track

The informal conversations in corridors, coffee queues and after-parties that many developers rate as the main value of a single-track community conference. Bring a short, specific problem to discuss.

18

Lightning talk

A short slot, typically 5 to 10 minutes, for a focused idea or demo. Community conferences use them to give first-time speakers a low-risk stage.

19

CFP (Call for Papers)

The open submission window through which speakers propose talks and workshops. Deadlines are announced on the organiser's site and social channels, usually months before the event.

20

Unconference / open space

A participant-driven format where attendees propose and vote on session topics on the day, rather than following a fixed speaker list. Common at community-run developer events.