Damjan Savić
Reference projects

HomeTechnologyReact

React in use

React with TypeScript, without a state-management library as long as the server holds the data. What stays in the browser is interaction — not a second copy of the database.

Full-stack development1 case study

Screencast · React in a running application
A detail from an application running in production.

Proven by

One published project with React — with stack, role and result.

2025

2,500

operations per day · one VPS

Case study: SnipeFlip

What that means in practice

React runs here only where the server cannot answer: the search palette, the language switcher, the video facade, the consent card. No state library — the server holds the data, the browser holds the state of one interaction. That keeps the amount of JavaScript small enough for a page to stay readable without it.

  • React 19 with Server Components

  • TypeScript-first development

  • Custom Hooks & Composable Architecture

  • State Management (Zustand, Redux)

Screencast · React in a running project
In operation, recorded in a running project.
Screenshot · the React setting you only learn after the first deploy
The setting you only learn after the first deploy.
Screenshot · the error React produces the first time
The error the first time round — and what fixes it.

Other technologies

Contact

Half a minute, and you know more.

Half a minute on what I work on and how. If a question is left, write to me — an answer within one working day.

Get in touch

Or write directly:info@damjan-savic.com