5 ms·
I think I may have a better idea for the HUD. I'm on OS X right now, and I use Spotlight for absolutely everything. The help menu has a feature to Spotlight wi
by chrisdroukas 15y ago
I think I may have a better idea for the HUD.
I'm on OS X right now, and I use Spotlight for absolutely everything. The help menu has a feature to Spotlight within menus, but it's not great if you don't know the literal name of the command (like save or open). Things can get complex quickly in robust applications.
What about appending alternative names to menu commands as metadata, so when a user searches for 'paint bucket' in Photoshop, they're driven to 'fill'. I'd imagine that's the easiest way to map intent to action. Further still, make menus public data-driven — learn common intent by what users search for and end up clicking on.
The use cases for this might be small, but the benefit of keyboard shortcuts is in discovery. Users should be able to articulate to applications what they intend to do.
Edit: If this exists already, we're living in the future.
- Schlaefer 15y ago> Edit: If this exists already, we're living in the future. Try the OS X System Preferences search field. It's there since 10.4ish?
- chrisdroukas 15y agoThat globally would be amazing.
- aaimnr 15y agoI don't remember any example right now, but lot of system utilities in Windows 7 has such an alternate description in metadata discoverable through Windows start search input. I've found similar behaviour in IOS - I've typed 'pocket' into IOS spotlight to launch PocketCasts app forgetting that it changed name to Casts. The app has been found nevertheless.