What hurts now
- Design changes are blocked by release cadence.
- Token drift compounds across apps quietly.
- Component package maintenance eats engineering time.
For Developers
Design updates shouldn't wait for deploys
Strata imports Figma or Style Dictionary, generates tokens plus component definitions, and delivers them through React packages and Web Components with build-time or 3-second runtime sync.
What changes
Runtime mode updates both token values and component structure. Build-time mode gives locked, versioned releases. You choose control model per product surface without splitting your design system definition by framework.
Build-time vs runtime
Build-time sync
Compile tokens and components at deploy time. Ideal when release governance is strict.
Runtime sync
Poll every 3 seconds and apply updates live, including structural component changes.
Structural update moment
// existing app usage <CheckoutAction /> // system definition update CheckoutAction: Button -> Input // consuming apps update live in runtime mode // no app redeploy required
Install options + init
npm install @strata/react @strata/web-components
import { StrataProvider, useStrataComponent } from '@strata/react'
<StrataProvider api="https://your-project.strata.io">
<App />
</StrataProvider>
const Button = useStrataComponent('Button')
// Non-React apps can register the same system
import '@strata/web-components'