Skip to content

Display ETA and details when starting a workspace #3738

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

Open
shaal opened this issue Apr 5, 2021 · 8 comments
Open

Display ETA and details when starting a workspace #3738

shaal opened this issue Apr 5, 2021 · 8 comments
Labels
component: dashboard meta: never-stale This issue can never become stale type: improvement Improves an existing feature or existing code

Comments

@shaal
Copy link
Contributor

shaal commented Apr 5, 2021

Today, there are very little details, on what's happening, or what should the user wait for, while a workspace is being prepared.

I read some interesting explanations, Workspace Life-Cycles on this page -
https://www.notion.so/Redesign-Loading-Screen-5e2f3a45cb5446088566af1b30cde55f

I think it will be a nicer experience, to know what to expect, when that is possible.
If you think it's overwhelming amount of information, It could be minimized by default, and the user can open for details.

During a prebuild, a user can at least see the commands that are running, so even that ETA is unknown, the user can tell where the process is at according to what is running in the terminal preview screen.

The other steps, like Acquiring Node, and Pulling Docker Images, can take more than a few seconds, so having details like ETA, average time for that task, and a count of MB downloaded out of total image MB - would make waiting a better experience, because it's no longer unknown, or feel like it's stuck, the user would know more about what is happening.

@svenefftinge
Copy link
Member

Yes, showing an ETA would be great. We don't have that information ATM, unfortunately.

@JanKoehnlein JanKoehnlein added component: dashboard type: improvement Improves an existing feature or existing code labels May 31, 2021
@stale
Copy link

stale bot commented Aug 29, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Aug 29, 2021
@shaal
Copy link
Contributor Author

shaal commented Aug 30, 2021

Requesting to add meta: never-stale label to this issue

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Aug 30, 2021
@gtsiolis gtsiolis added the meta: never-stale This issue can never become stale label Aug 30, 2021
@gtsiolis
Copy link
Contributor

Added never-stale label although providing an ETA still sounds hard to tackle and potentially has a low impact for the users.

Instead focusing on improving the a) user experience and b) perceived performance of the loading screen while c) minimizing the start-up time sounds more realistic and impactful. ↪️

@shaal
Copy link
Contributor Author

shaal commented Aug 30, 2021

Thank you @gtsiolis.
ETA would be great, but if it's not possible to know the exact numbers, I would suggest a visual ETA.

Currently, when waiting for workspace to start, Gitpod displays 3 bars, with 1 written status line above it. There's no way to know if it's going to take 5 seconds or 30.

I think the display, when starting a workspace can be improved by:

  • Display the list of all steps that are going to happen (I think displaying any step that takes over 3 seconds would be nice)
  • Display a checkmark for any step that was completed.
  • For each step display a bar filling up
    The rate of how fast a bar gets filled up would be determined by the worst-case-scenario estimation. That way, when a step might take 30 seconds, the bar start filling up, and even if it's much shorter, like 5 seconds, the user will be happy to see a step completed, and the new step started.

A nice addition to that, is if a certain step takes MORE than the worst-case-scenario estimated, the user would get a friendly message that something is not working correctly, with suggested steps on how to get unblocked (refresh? try again? submit a ticket)

@atduarte
Copy link
Contributor

atduarte commented Aug 31, 2021

Another benefit of changing the loading screen could be (1) that we make the distinction between when a prebuild is used and when it's not clearer, (2) easier to understand if something is stuck.

Example interface (from Vercel) with process steps, time, and some associated logs:

Default Expanded
image image

@JohannesLandgraf
Copy link
Contributor

@shaal and myself did a demo today and received the feedback that showing more information here / being more transparent would help a lot

@loujaybee
Copy link
Member

I think this is related, or a duplicate of:

The linked issue is a bit more specific, to define these events, but this issue looks like it's about having them viewable on workspace start. The two are certainly related and/or solving similar challenges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: dashboard meta: never-stale This issue can never become stale type: improvement Improves an existing feature or existing code
Projects
None yet
Development

No branches or pull requests

7 participants