React development
How does AonHive use React?
React development for complex browser interfaces and design systems.
React is the interface. The record lives in the database. A component may render a fare, a status, or a list. It does not get to decide them. We split server data, the URL, and short-lived UI state so a refresh and a second tab still show the same fact. On Reycona the shop renders the catalog. The order is priced in checkout_cart from the product row. On the Sevenco site the city chip restores a stored city only when that city is marked available. On the Sevenco admin desk a status change writes the ride row, then the earnings query is invalidated.Discuss this stackHow we use it
The screen does not own the row.
- 01
Name the state
A query owns data the server can change. The URL owns filters and the open row. Local state owns a draft that has not been saved. One store for all three is how a screen drifts from the record.
- 02
Keep a long list cheap
Dispatch and ledger screens virtualize. A heavy update goes through a transition so typing and navigation stay responsive. We check that on a mid-range laptop, not only on a fast dev machine.
- 03
Ship the states the product uses
Empty, loading, error, and forbidden are part of the component. A row the person cannot open is a state, not a missing design.
React
Bring the system this has to fit.
Tell us the product, the estate you already run, and what your team needs to own. We will say whether this belongs in the stack.