Background
There are currently multiple progress elements used across different projects (check the inventory), which can complicate their usage and lead to inconsistent experiences:
- Elevated determinate progress bar
- Inline indeterminate progress bar
- Bouncing dots
- Spinner (used to load sections in pages, and also next to texts)
- Skeleton
- Pending states within components (bars indicating pending state, currently used in OOUI components)
To simplify and unify progress communication, we should evaluate reducing the number of progress elements in Codex. Once we finalize how to consolidate the progress elements, we will need to document clear guidelines in Codex with best practices for their use.
User stories
- As a designer and developer, I need a clear understanding of which progress component to use for my project.
- As a user, I want progress elements to be consistent across projects to improve my experience.
Open questions
Add here the questions to be answered in order to design and implement the component