Web Frontends
What runs in the browser: applications, portals, websites — fast, including on poor devices.
- React
- Astro
- Measurably fast
How it works
We choose the technology according to what the page has to do, not the other way round.
Application or page
An application with sign-in, state and heavy interaction we build with React. A page that mainly shows content we build statically with Astro: faster, cheaper to run, and without moving parts that can break. That decision is made per area, not per project.
Speed is a requirement
For us load time belongs in the acceptance criteria like any other requirement. We measure against real conditions, not on a developer machine with fibre.
Usable without a mouse
Keyboard operation, focus order, labels for screen readers — this is the implementation of what the concept phase settled under accessibility, not a later addition.
On the device your users actually have
We test on mid-range devices and throttled connections. What runs well there runs well everywhere. The reverse does not hold.
- The browsers and devices you have to support. Corporate customers occasionally bring surprises.
- Content, if there is an editorial surface — copy rarely arrives on time.
A deployed application, measurably fast, with the source code in your possession.
If you skip this
A frontend whose speed is only checked at the end is usually too slow. Optimising afterwards generally means rebuilding, not polishing.
Where this came up
LIQIDReact reinforcement in the team of an asset manager.
View case studyQuestions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.