What We Build with React
- customer, partner and employee portals;
- admin panels, CRM-style systems and dashboards with charts;
- online services where users configure, book or calculate something;
- marketplace and catalog interfaces with lots of filters;
- embedded widgets: a calculator, a product configurator, a location map.
When We'd Recommend Something Else
- Your team or project is already on Vue, or a small team needs a simpler start: it makes sense to stay with Vue.js.
- A large enterprise system where strict conventions and a uniform structure for many developers matter: consider Angular.
- A content website that only needs a few interactive elements: a CMS plus a bit of JavaScript is better than a React app.
Design System and Component Library
In a large interface, inconsistency is the most expensive problem: ten button variants, different spacing, tables that behave differently. We solve this with a component library that matches your design in Figma. Every component has documented states and variants, and new screens are assembled from ready-made parts. A change to the design system is carried into code once, not patched on every screen.
Speed and Accessibility
It is easy to make a React app heavy, and on a budget smartphone a heavy portal opens with a noticeable delay. So we split code into chunks that load only when the user navigates to a section, replace heavy libraries where a lighter alternative will do, show a page skeleton instead of a blank screen, and render long lists and tables in portions. We also pay attention to accessibility: proper field labels, keyboard navigation and sufficient text contrast.
New Interface or Improving an Existing One
A new project starts with user scenarios and a component set, not with picking trendy libraries. From the outset we set up TypeScript, code formatting rules and error tracking from users' browsers.
An existing project is assessed first: React and library versions, the size of the code shipped to the browser, the causes of slow screens and test coverage. Old class components, outdated libraries or builds on unsupported tooling are migrated gradually, alongside new feature development.
What to Prepare Before Kickoff
- Your design files in Figma, if you have them, or a description of the key user scenarios.
- API documentation, or a description of the backend if the API still has to be built.
- For an existing project: repository access and a list of known problem screens.
- Requirements for browsers, devices and accessibility.
What Affects Cost and Timeline
- The number of screens and their states, not just the number of pages in the mockup.
- Backend readiness: whether a documented API exists or has to be built in parallel.
- Complex elements: editable tables, charts, drag and drop, offline mode, real-time updates.
- Design: whether there's a design system or components need to be designed alongside development.
- Accessibility requirements and support for older browsers.
After reviewing the task, we break the work into phases and explain what each one includes.
Frequently asked questions
How is React different from Next.js? React is a library for the interface. Next.js is a framework built on React that adds pages, server-side rendering and SEO capabilities. A customer portal only needs React; a public website more often needs Next.js.
Can React be added to an existing CMS website? Yes. A standalone interactive block (a calculator, configurator or filter) can be built in React and embedded in a page without rewriting the site.
Can React handle an interface with thousands of data rows? Yes, if rendering is organized properly: show only the visible part of the table, load data in batches, and avoid re-rendering the whole list when one row changes.
Can an old interface be rewritten in React gradually? Yes. We build new sections in React and embed them in the existing system, and move old ones over as they need changes anyway. That way product development doesn't have to stop for a rewrite.
Can we later build a mobile app on the same logic? Yes. Approaches and some of the logic carry over to React Native for iOS and Android apps.
Will we get code another team can maintain? Yes. We write in TypeScript, follow widely used practices and document components, so the project can be handed over to other developers.
Why Promodex
Our portfolio includes METEC and Supermarket Krasy, as well as Komoot and OpenSea, which we contributed to. Designers and developers work on one in-house team of 30+ people with no outsourcing, so Figma mockups and code components stay in sync. We justify our library choices rather than impose them, and after launch we keep improving the interface. Promodex has been delivering projects since 2015, 750+ so far.