React development
React, built so the next team can still work on it.
React built the boring way: clear state boundaries, components documented well enough to reuse, bundles measured rather than assumed, and rendering chosen to suit the page. It should be handed to another team without an apology.
Overview
React, the way we do it
React is the safest default for most interfaces, and the easiest thing in the world to build badly. The failure is rarely the library: it is state spread across forty components, a bundle nobody has looked at since launch, and a codebase only its author can change. The result is a product that is slow to load and slow to add to.
We build React the boring way. Clear state boundaries, components documented well enough to reuse, bundles measured rather than assumed, and rendering chosen to suit the page rather than the fashion. It should be handed to another team without an apology.
What's included
What you actually get
- Component libraries your developers can build on, not just consume
- Bundle size and load time measured on a mid-range phone
- Server rendering where a page needs to be found, client where it does not
- Right-to-left Arabic handled in the components, not patched over
- TypeScript throughout, so a change breaks the build rather than production
How we work
Five steps, no surprises
- 01
We talk
A call or a WhatsApp thread. You tell us what is not working; we tell you honestly whether we are the right people.
- 02
We scope it
A written plan with what you get, what it costs and how long it takes. Fixed, so there are no surprises later.
- 03
We build it
You see it as it goes, not at the end. Changes are cheap while it is still being built.
- 04
We put it live
On infrastructure we set up and secure, tested before the launch date.
- 05
We keep it running
Updates, monitoring and someone who answers. Most clients stay on a monthly agreement.
Questions
About react
React or Angular?
React if you want the larger hiring pool and more freedom in the architecture; Angular if you want more decided for you and a stricter house style. We build in both and will tell you which suits your team rather than which we prefer.
Can you join a React project already underway?
Yes. We start by reading it and telling you what we find, including if the honest answer is that it needs restructuring before features get added.
Do you use Next.js?
Where server rendering earns its keep, which is most public-facing sites. For an internal dashboard behind a login it usually does not, and plain React is simpler to run.
Also
Related work
- Quality AssuranceFind it before your customers do.
- UX DesignWork out what it should do before anyone builds it.
- UI DesignScreens people can use without being trained.
- Design SystemsOne set of rules, so the tenth screen looks like the first.
- Mobile ApplicationsApps people keep on the first screen.
- iOSiPhone apps built the way Apple expects.
- AndroidAndroid apps that work on the phones people actually own.
- FlutterFlutter, when one team has to cover both stores.
- AIAI that does one job, properly.
- Machine LearningModels that earn their place in the business.
- Data ScienceAnswers from the data you already have.
- LLMsLanguage models, kept on a short leash.
- Generative AIGeneration with a human still holding the pen.
- PythonPython, for the work that has to be read as well as run.
- Back-EndWhere an order becomes an order.
- DatabaseThe part of your system that is hardest to fix later.
- Node.jsNode.js, for the systems that have to answer quickly.
- GoGo, where it has to be fast and stay simple.
- .NET.NET, for the systems a business runs on.
- JavaJava, for systems measured in decades.
- Front-EndThe half of your product people actually see.
- Web DevelopmentCompany sites, customer portals, and web systems that hold up.
- AngularAngular, for systems that have to last.
Tell us what you have in mind.
An engineer reads your message and replies to you directly.
Talk to us