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

Consolidate and update built-in walkthrough content #197503

Closed
daviddossett opened this issue Nov 6, 2023 · 5 comments · Fixed by #197689
Closed

Consolidate and update built-in walkthrough content #197503

daviddossett opened this issue Nov 6, 2023 · 5 comments · Fixed by #197689
Assignees
Labels
getting-started insiders-released Patch has been released in VS Code Insiders ux User experience issues
Milestone

Comments

@daviddossett
Copy link
Contributor

I observe a few bits of low-hanging fruit that we could go after to improve the built-in walkthroughs. As they stand today, I noted that:

  • 3 distinct walkthroughs feels like a lot—and is probably asking for a big drop off after the first one
  • New user pain points (getting started content, pointer to settings) are buried

What if we consolidated the 3 walkthroughs into 1 or 2, and had a pointer to docs/YouTube/etc. for some of the additional content? We could also pull up steps related to intro videos and settings as part of the changes.

cc @bhavyaus

@daviddossett
Copy link
Contributor Author

Preview of initial changes proposed in #197689:

CleanShot 2023-11-07 at 15 27 22@2x

CleanShot 2023-11-07 at 15 29 01@2x

@vscodenpa vscodenpa added the unreleased Patch has not yet been released in VS Code Insiders label Nov 8, 2023
@sandy081
Copy link
Member

sandy081 commented Nov 9, 2023

This pushed Settings Sync down in the list. Any reasoning for this?

CC @isidorn @bhavyaus

@daviddossett
Copy link
Contributor Author

  1. Settings sync is almost certainly an unexpected concept be presented with when installing and opening VS Code for the very first time. The getting started walkthrough was intentionally designed to have users step through the basics—theme, lang extensions, open a folder, etc. Settings sync is important, but I strongly oppose this being first in the list.
  2. These latest changes pulled the Settings UI and tutorial videos steps into the 1st walkthrough in response to the NPS verbatims claiming users couldn't find or understand those things. After pulling in the Settings step, it makes sense to co-locate settings sync with it. In fact, I'd actually consider putting both CTAs on the same setp (Open Settings | Backup and Sync Settings). For the moment they are still discrete steps.

I'm more than happy to play with the positioning. I just don't think it should be first just to move a metric.

@daviddossett
Copy link
Contributor Author

This is a devtools hack, but you get the idea. We could have a shared step e.g.

Image

Just one idea!

@vscodenpa vscodenpa added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Nov 10, 2023
@IAmHopp
Copy link

IAmHopp commented Dec 1, 2023

Just to add my experience here: It just so happens I recently installed Insiders on a new machine and I saw this page for the first time. I understand if it stays that way if it's backed by user research, but it did confuse me that retrieving my synced settings wasn't the first thing that was proposed to me.

To be clear, I didn't know it was the first option before because I haven't gone through the first-use experience in a long, long time. But it was my immediate expectation.

The first thing it asked me for was choosing a theme. And, well, if I already have that setting saved in the cloud...

@github-actions github-actions bot locked and limited conversation to collaborators Dec 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
getting-started insiders-released Patch has been released in VS Code Insiders ux User experience issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants