React
The library behind most of the interactive web, and the backbone of our web and mobile work.
What we build with it
- Dashboards and admin panels
- SaaS product frontends
- Browser-based tools
- The UI layer of our React Native apps
Why we use it
React's ecosystem means there's a maintained library for almost anything, and any developer you hire after us will already know it. We pick it when an app has enough interactive state to need it, which covers most product UIs.
When we don't use it
A mostly-static site doesn't need React running in the browser. For marketing and content sites we reach for Astro, which is what this site runs on, and ship pages with almost no JavaScript.
What we have written about React
- Server Actions or API routes in Next.js
Server Actions cover most mutations in a Next.js app, but webhooks, third-party callers, and non-React clients still need a real route. Here's how we decide.
- Svelte 5 runes vs React hooks: we write both every week
A mental-model comparison of Svelte 5 runes and React hooks, based on two things we maintain: this site's Svelte island and FurnitureAxis's React 19 frontend.
Questions clients ask
Short answers, no sales language. If yours isn't here, ask an engineer directly.
Ask us anythingWhy React instead of a newer framework?
Ecosystem and hiring. Newer frameworks are often nicer in isolation, but React's libraries, documentation, and talent pool save real money over a product's life. Where a lighter tool clearly wins, we use it and tell you why.
Do you use TypeScript?
Yes, on everything. Types catch a whole class of bugs before the code runs and make handover to your future team much easier.
Got something to build?
Tell us what you need. An engineer replies, not a sales team.