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

Make the VSCE experience feel more native to VS Code #30207

Open
jjinnii opened this issue Jan 25, 2022 · 2 comments
Open

Make the VSCE experience feel more native to VS Code #30207

jjinnii opened this issue Jan 25, 2022 · 2 comments
Assignees
Labels
integrations needs-design Design requests - add to 'design priorities' project, add a deadline, if possible.. needs-feedback Needs additional feedback vscode-extension

Comments

@jjinnii
Copy link
Contributor

jjinnii commented Jan 25, 2022

Feature request description

Based on internal feedback, the current implementation of the extension feels not native to VS Code. This is a result of using Sourcegraph UI components, pulled in from webview, instead of utilizing VS Code's native UI elements. As a user of VS Code, I like and appreciate when my extensions feel native and seamless to my editor.

It is our hypothesis that improving the "native" integration of our extension will improve recurring usage.

Describe alternatives you've considered.

@olafurpg's original version of the extension utilized notebooks to create a search experience that felt very native to VS Code. However, the team moved forward with a Webview implementation based on the technical restrictions that came with notebooks as well as QuickPick.

Additional context

User testing also uncovered that just exposing the Sourcegraph search input field (even if it looks "native" to vS Code) makes it extremely difficult for users who are new to Sourcegraph to understand how to use the extension. There was a user need here to onboard and teach users about Sourcegraph and how to use the extension, within the extension itself.

Based on this:

  • How might we make the extension feel more native while maintaining the webview implementation?
  • How might we include features to help new users onboard and promote account creation, but still have the extension feel native to an editor?
@jjinnii jjinnii added needs-design Design requests - add to 'design priorities' project, add a deadline, if possible.. integrations vscode-extension labels Jan 25, 2022
@jjinnii jjinnii self-assigned this Jan 25, 2022
@jjinnii
Copy link
Contributor Author

jjinnii commented Jan 25, 2022

Relevant internal thread on VS Code's new webview UI toolkit. @tjkandala @abeatrix is this essentially a "component library" that looks/feels VS Code native? Would it be possible for us to plug and play here with our current implementation? i.e. replace an input field with a component from this toolkit, for example.

@abeatrix abeatrix added this to the VSCE v1 milestone Jan 26, 2022
@jjinnii jjinnii removed this from the VSCE v1 milestone Feb 1, 2022
@jjinnii jjinnii removed their assignment Feb 1, 2022
@jjinnii jjinnii added the needs-feedback Needs additional feedback label Feb 11, 2022
@philipp-spiess
Copy link
Member

@jjinnii Hey Sara! We're currently triaging old issues and came across this one and are unsure how to proceeded. What is your suggestion? Is this still a big enough issue for us to work on? How much did the last minute VS Code theming effort help here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integrations needs-design Design requests - add to 'design priorities' project, add a deadline, if possible.. needs-feedback Needs additional feedback vscode-extension
Projects
None yet
Development

No branches or pull requests

3 participants