UI & Frontend Bridge
Where the service meets a screen: annotations and data binding, the launchpad, theming and localization, and what a UI needs from the backend to render.
Capabilities
Hosting a frontend's built static files behind a login
Serving a frontend and its backend services from one local origin
Changing a delivered app as layered changes that survive upgrades
Turning a URL hash into a view and back in a single-page app
Screens where a person approves a workflow or process task
Consistent visual identity across controls, including custom themes
Making a UI usable with a screen reader or a keyboard alone
Custom controls, wrappers and icon fonts packaged for reuse
Keeping a control and a model in step in both directions
Describing a service so a Fiori client renders it without UI code
Finding why a browser UI is slow to start or respond
Getting apps, cards and pages in front of users in a launchpad
Extending an application launchpad's shell
Serving labels, messages and content per user locale
Operating an app by finger, stylus or gloved hand
Using standards-based custom elements inside an app
Rendering a UI on the server before it reaches the browser
Recent changes
All changes →App hosting coverage reassessed
Backend on the dev server coverage reassessed
Custom controls and libraries core coverage reassessed
Data binding core coverage reassessed
Launchpad and site content coverage reassessed
Launchpad plugins core coverage reassessed