React

React when the context calls for it

React is a JavaScript library for building user interfaces out of reusable components. It was created to solve the problem of keeping complex screens in sync with changing data: you describe the interface declaratively and React updates only what needs to change. Around it grew the largest library ecosystem on the front end, with a mature, well-documented package for almost any need.

Our preferred front end is Vue, and we are upfront about that. But we choose tools by the problem, and there are contexts where React is the right answer: your team already works in React, the product depends on specific libraries from its ecosystem, or there is an existing React codebase that needs to evolve. In those cases we work in React with the same rigor we apply to any stack.

For you, that means continuity instead of a rewrite. An inherited React project does not have to be migrated to our favorite stack: we step in, understand the code, clean it up and move it forward. And because React is one of the most widely adopted front-end libraries, hiring and training a team to maintain the product later tends to be simpler.

• Rich, reactive web interfaces
• Complex single-page applications (SPAs)
• Dashboards and data visualizations
• React front ends for Laravel APIs
• Evolving existing React codebases