Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visual Feedback for Update Processes on the "Captain" Platform #242

Closed
pixelass opened this issue Apr 30, 2024 · 1 comment · Fixed by #243
Closed

Visual Feedback for Update Processes on the "Captain" Platform #242

pixelass opened this issue Apr 30, 2024 · 1 comment · Fixed by #243
Assignees

Comments

@pixelass
Copy link
Member

Is your feature request related to a problem? Please describe.
Yes, there is a user experience issue with the update process on the "Captain" Platform. Currently, when checking for updates, there is no immediate visual feedback to indicate that the system is processing the request. This lack of feedback can be confusing as the "Update now" button only changes after a delay, and clicking it initially seems to have no effect because nothing appears to happen for some time.

Describe the solution you'd like
I would like the platform to include a visual indicator, such as a spinner or progress bar, when checking for updates and when the "Update now" button is clicked. This indicator should be prominent enough to reassure users that the system is actively processing their request.

Describe alternatives you've considered
An alternative would be to implement a status message or notification area on the update screen that provides textual feedback such as "Checking for updates..." or "Update in progress..." This could be used in addition to or instead of a spinner.

Additional context
Adding visual feedback during the update process will significantly enhance the user experience by making it transparent and reassuring users that their actions are being processed. This change will help prevent confusion and repeated clicks, which could potentially lead to system errors or duplicated processes.

pixelass added a commit that referenced this issue Apr 30, 2024
@pixelass pixelass self-assigned this Apr 30, 2024
pixelass added a commit that referenced this issue Apr 30, 2024
## Motivation
give users visual feedback when checking for updates

## Issues closed

closes #242
TimPietrusky pushed a commit that referenced this issue Apr 30, 2024
# [1.0.0-alpha.59](v1.0.0-alpha.58...v1.0.0-alpha.59) (2024-04-30)

### Features

* visual feedback when checking for updates ([#243](#243)) ([b6aa22e](b6aa22e)), closes [#242](#242)
@TimPietrusky
Copy link
Member

🎉 This issue has been resolved in version 1.0.0-alpha.59 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants