Product-form decision guide
Use UI source when you need one focused interface capability that your team can inspect, adapt, and own. Use a component library when many product surfaces need a maintained system of shared primitives, tokens, and APIs. Use a template when you need a broad preassembled page or application structure and are willing to reshape its architecture. vro.dev currently publishes item-level React component source—not a maintained design-system library or a template catalog—so evaluate each record as a focused starting point, then test the delivered version in your project.
The definitions and decision matrix compare product form rather than visual style. The vro.dev conclusion is based on the canonical public catalog and three exact published React records reviewed on the stated date. Only product types represented by current public records are shown as vro.dev examples; an empty navigation surface is not treated as published inventory.
Reviewed: by vro.dev product-form and live-catalog review. Correction owner: support@vro.dev.
| Product form | Typical scope | Dependency model | Update model | License check |
|---|---|---|---|---|
| UI source | One focused capability | Local code plus declared packages | Your team ports or reapplies changes | Exact files, version, receipt, and redistribution boundary |
| Component library | Shared primitives and systems | Maintained package and conventions | Versioned upgrades and migrations | Package, asset, trademark, and commercial-use terms |
| Template | Page, flow, or application shell | Broad architecture and fixture set | Fork, reconcile, or intentionally diverge | Code, fonts, media, demo content, and resale restrictions |
vro.dev currently publishes item-level React component source. The reviewed public inventory does not establish a maintained design-system library or a template catalog. Use another source when the project needs those broader product forms.
Offer an accessible monthly date chooser with availability states, keyboard movement, a selected-date summary, and a caller-owned scheduling callback.
Product form: UI source component · React 1.0.0
Dependencies: lucide-react, react
Use when: An existing React product needs an adaptable availability-selection surface.
Boundary: It is not a booking backend, timezone authority, or complete scheduling application.
Introduce a software platform through compact navigation, a precise conversion hierarchy, and an original code-native product workspace receding into a perspective runway.
Product form: UI source component · React 1.0.0
Dependencies: react
Use when: A React marketing surface needs a distinctive product-workspace hero direction.
Boundary: It is not a full marketing template, design system, or production content strategy.
Visualize a live agent execution plan as nested tasks, status changes, dependencies, and assigned tool labels without implying remote execution.
Product form: UI source component · React 1.0.0
Dependencies: lucide-react, react
Use when: An AI-assisted product needs a focused plan-tree interaction to integrate with its own state and agent runtime.
Boundary: It is not an agent backend, orchestration SDK, or complete application shell.
This is a dated selection guide, not a claim that one product form is universally better. Catalog inventory, source versions, dependencies, licenses, and access states can change. Recheck the canonical record and controlling license before use. A public preview does not contain protected source, and entitlement-protected delivery does not make vro.dev a package registry, design-system vendor, or template marketplace.
What is vro.dev? · Source-backed inspiration · Production-readiness checklist · Licensed source guide · Metadata audit · Public catalog · Report a correction