[FEAT]: Improve Survey Progress Bar Clarity #6214
Merged
+48
−27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does
This PR enhances the survey progress bar to make its meaning more intuitive for users. Based on issue #938,
users found the progress bar unclear. To address this, the following improvements have been made:
Screenshots
Before:
After:
Screencast.from.2025-02-25.19-31-05.webm
Additional Description
Yes, you were right @ragesoss. If the indicator with checks/circles for each question (the last proposed option) is implemented then the users might be confused about why the progress bar updates by a larger number of questions—including conditional ones—when they have only answered a single question. This could lead to misunderstandings about how progress is measured.
Therefore, in place of that I have implemented the progress bar with percentage completion and have tried to revamp it.
Let me know, if this approach isn't satisying enough, we can try something else.