Display ETA and details when starting a workspace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked “Workspace Life-Cycles” explanation and the current workspace preparation experience, including the terminal preview. Define which preparation steps should expose progress, ETA or download details, and how expanded versus minimized information should work. Done means the waiting experience communicates meaningful progress for the supported steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100