platform-guideline 1 linked patterns checked
SAP Fiori for Android Step Progress Indicator
Documents step progress indicator usage for horizontal and vertical mobile views, short step names, dynamic dependent sub-steps, visible continuation affordance in scrollable indicators, and avoiding misleading total counts for dynamic steps.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Step progress | Choose step progress when users need status for named workflow stages, not only a route position. | The indicator reads from the same workflow state that controls route availability, validation, saved answers, and submission gates. | SAP Fiori supports mobile step progress indicators with short labels, dynamic dependent steps, and guidance not to count dynamic steps in totals prematurely. |
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: SAP Fiori Design System. Last checked: .