Something that comes up a lot is that the quick pick is non-local, and it's easy to miss when triggered through a UI control (as opposed to by the user through a shortcut). The problem gets worse on large/multiple screens. In addition to that, the cross-platform (webview) menu possibilities are very limited. It's not possible to use icons, groups, description etc. And in a webview menus are static and must be predefined.

QuickPick guidelines: https://code.visualstudio.com/api/ux-guidelines/quick-picks

Considerations:

• Benefits?
  • Filter functionality
  • Filter placeholder text serves as menu title
  • Group labels
• When?
  • Do use for variable lists (like branches, repositories, files, folders, etc.)
  • Do use for recents/favorites/suggested
  • Don't use it as a replacement for a menu
• Limitations/problems/misuse?
  • Don't add more than 3 other actions (e.g. "Create Branch" at the top of a list of branches)
  • Don't use submenus or multiple steps
  • No shortcuts
  • Should not be combined in any way with native menus
  • Should only be able to triggered through a main UI element.
  • Should not be used to list a set that's always the same
  • Multistep allowed?
• Specs?
  • New guidelines: filter field MUST have a descriptive placeholder text, mentioning what is being picked and what for: For example: Select a color for profile 'Ruby' or Select a milestone for this pull request
• Simplified placeholder label? e.g. just "Milestone"
• Properties? width/height/euro
• Setting: Allow Local QuickPick

Mockup:

This would essentially be a very powerful menu, but using existing QuickPick APIs.

cc @daviddossett