Open isidorn opened 1 year ago
In a recent user study, we observed participants getting "stuck" in vscode.dev when trying to import a profile. User behavior was to click on the GitHub gist link thinking it would lead them to their local VS Code. Users were confused once they were in the browser and would install the profile in vscode.dev. They would then try to transition to VS Code but struggled to find successful transition points. Once they reached this point in the browser, there was a hard edge and participants were unable to navigate back.
I like the idea of defaulting the button to "Import in Visual Studio Code".
@cwebster-99 thanks for sharing, this is super insightful. @sandy081 what are the main benefits of showing vscode.dev here? In theory, could we skip it and go directly to vscode?
fyi @joaomoreno
In theory, could we skip it and go directly to vscode?
I am not sure it is possible in practical. @joaomoreno is it?
I think switching the default button makes sense. I would consider doing this.
Using vscode.dev is a great way to preview the profile, so I wouldn't drop using it as a stepping stone. But it feels like the actual UX needs polish, if users aren't aware of what's actually happening and how to proceed to the Desktop.
As we discussed, we should