Metadata-driven UI competitor research¶
Research snapshot: 2026-07-15. Primary product/developer documentation was used. The goal is to select durable platform patterns, not reproduce any competitor.
| Platform | Evidence | Adopt | Adapt or reject |
|---|---|---|---|
| Salesforce | UI API returns data and layout metadata with permissions and form factor; Dynamic Forms composes individual fields and sections with visibility rules. | Runtime metadata shaped for the caller; fields, sections, actions, modes, and device context. | Keep typed plugin resources instead of a global Salesforce-style object engine. |
| Dynamics / Dataverse | Model-driven forms provide several form types; PCF supplies code components; form ALM supports differential layers. | Reusable components, distinct modes, publish lifecycle, and layered customisation. | Use JSON contracts and stable IDs rather than exposing FormXML as the public authoring model. |
| ServiceNow | UI Builder components combine layout, components, bindings, visibility, and events; data resources separate data acquisition from presentation. | Explicit data sources, bindings, events, reusable components, and audience variants. | Reject arbitrary page scripts and per-node CSS in ordinary metadata. |
| HubSpot | UI extensions target named locations, use a host component library, and run custom React in a secure sandbox. | Named extension locations, controlled SDK, passed context, and isolated custom UI. | Declarative host rendering is the default; the sandbox is an escape hatch rather than the main form system. |
| Odoo | View records define form, list, kanban, calendar, graph, pivot, and other views and apply ordered inherited patches. | Multiple views over a resource and additive inherited customisation. | Replace brittle XPath targets and executable Python expressions with stable IDs and a bounded AST. |
| Zoho CRM | Page layouts vary by profile and record layout; widgets provide custom embedded UI. | Audience variants, conditional layouts, quick-create/detail forms, and an embed escape hatch. | Do not reproduce inconsistent rule support across entry points; the same authoritative rules apply to every operation. |
| Pipedrive | App extensions offer predefined JSON panels/modals and iframe-based custom UI in named locations. | Simple declarative surfaces plus an isolated bespoke surface. | Generalize beyond CRM detail panels so the contract also serves portals, settings, scheduling, and future service operations. |
| SAP Sales Cloud | The extension guide supports adaptation and mandatory/read-only extension-field behavior. | Governed administrator adaptation. | Avoid product-specific extension-field limits in the platform contract. |
| Oracle Fusion | Application Composer creates and modifies application pages and layouts for standard and custom objects. | Separate design-time composition from published runtime pages. | Avoid coupling the renderer to a single enterprise object catalogue. |
Cross-platform conclusions¶
- Resource/field metadata, page composition, data operations, and custom code are separate concerns even when a product's tooling presents them together.
- Pages need stable component trees, reusable fragments, variants, explicit data binding, actions, and lifecycle—not only lists of fields.
- Layered patches inherit vendor/plugin improvements better than full tenant clones, but only when anchors and conflicts are deterministic and diagnosable.
- Permission-filtered server metadata is safer than sending everything and relying on client visibility rules.
- A bounded host component library provides consistency and accessibility; rich customer code requires origin isolation and mediated capabilities.
- Limiara should support diverse view types while retaining typed plugin-owned persistence rather than creating a lowest-common-denominator object engine.