Web Components interop

SAP publishes UI5 Web Components itself as the element set this flavor is built from, with official tutorials for React, Angular and Vue and a dedicated React wrapper, UI5 Web Components for React, that ships a Fiori-compliant React implementation over the same elements. An Angular wrapper, ui5-webcomponents-ngx, existed too but is now deprecated in favour of Fundamental NGX.

Not covered: It stops at the elements: the project states it is 'not built on top of UI5' and 'not a successor of UI5', but a complementary, lightweight offering usable with any web framework. The concerns freestyle UI5 answers stay outside it: routingRouting and navigationcapabilityTurning a URL hash into a view, and a view change back into a URL — so a deep link, a browser back button and a refresh all land where the user expects in a single-page app.SAP only, OData data bindingData bindingcapabilityKeeping a control and a model in step in both directions, including the formatting, type conversion and validation that sit between the two.SAP and community, unassessed, the flexibilityKey-user adaptationcapabilityChanging a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.SAP only layer and launchpad pluginsLaunchpad pluginscapabilityExtending an application launchpad’s shell rather than an individual app: adding header buttons, user-menu entries, frame areas or background behaviour shared across the apps it hosts. A development sandbox for launching an app is a separate concern.SAP and community, unassessed.