When we use React.

For interfaces that keep changing while the user uses them: applications that live in the browser, administration and moderation panels, operational tools where people stay on the same screen for hours.

This is where it pays off: a lot of state to keep together, and one page that changes rather than reloads.

The same applies to equivalent tools: the choice depends on what already exists, not on a preference.

The technologies we work with

When we do not use it

When the page consists of content that changes little. An editorial site or a showcase does not need this, and using it makes them slower to load and more expensive to maintain.

It is the same principle that says: if something can be done with an off-the-shelf tool, it is better to use an off-the-shelf tool.

What we have used it for

The way we work is the same across technologies: peer review before release, separate environments, and automated pipeline checks. How we work

If you have a project to build, grow or recover: Build · Scale · Rescue

When we use React.

Sailsquare — 5 years on the platform, alongside their team.

Gallucci Editore — e-commerce built around the catalogue.