Tiles
Tiles are the clickable entry points on the Fiori launchpad that launch apps, and can display live information. Well-designed tiles make the launchpad both a navigation hub and an at-a-glance dashboard.
Use dynamic tiles for the counts users care about (turning the launchpad into a light dashboard), keep titles clear, and group tiles logically.
- A tile is configured with a title, icon, a target (the app/intent it launches) and, for dynamic tiles, a service that supplies the…
- Tiles live in catalogs (the pool of available apps for a role) and are arranged into groups/pages that users see.
- Static tiles: a fixed icon/title that launches an app.
- Watch out: Too many dynamic tiles loading the backend.
Kinds of tiles
- Static tiles: a fixed icon/title that launches an app.
- Dynamic tiles: show a live number (e.g. count of open orders) pulled via OData.
- KPI/news/custom tiles: richer content on the tile itself.
How tiles work
A tile is configured with a title, icon, a target (the app/intent it launches) and, for dynamic tiles, a service that supplies the live number. Clicking a tile triggers intent-based navigation to open the target app, often with parameters.
Tiles in catalogs and groups
Tiles live in catalogs (the pool of available apps for a role) and are arranged into groups/pages that users see. Administrators assign catalogs/groups to roles; users then get and can personalise those tiles.
Design tips
Use dynamic tiles for the counts users care about (turning the launchpad into a light dashboard), keep titles clear, and group tiles logically. Overusing dynamic tiles, though, adds backend load, balance insight against performance.
Common pitfalls
- Too many dynamic tiles loading the backend.
- Unclear tile titles confusing users.
- Wrong navigation target on a tile.