Each search is an opportunity to build experience needed to use search less.
The buttons are there for those who want to run fast and or efficiently.
Doing that well is a lot of work, but it also delivers high value.
Going search only can be super lean, which has to be compelling. Everything costs something though, and the cost here is no user becomes adept. There is a permanently fairly high Ccost of interaction.
This is how MacOS X's help menu search box has worked for over a decade, and it's brilliant. Type in a search and it shows you every menu item that matches, and rolling down the list shows you live where each menu item is.
I wish Spotlight search was similar - showing paths more readily, and making it easier to open the folder that contains the item that you want to look at.
Siemens is an old company who tends to get investments right. Apple uses Siemens design software, so who knows? Perhaps Apple had influence?
Great implementation!
At the time, I was in a heavy pre-sales role and would make the help system a part of the demo. I am pretty sure everyone saw high value there.
And talk about complex, with depth, subtlety! That program demands more than mere buttons can deliver!
And my own ability to use the tool improved dramatically. I have 20 plus years doing sales, service, and support. OTC, SDRC, UGS (Both those two now Siemens, Soludworks, Solid Edge...)
Hands down, these methods crush anything else I have seen.
Also, in terms of the geometry, how the system builds models, the feature version is stored with the features, and that version will build models in newer software, until migrated forward by a user.
It's very complex.
Siemens is an old company who tends to get investments right. Apple uses Siemens design software, so who knows? Perhaps Apple had influence?
Great implementation!
At the time, I was in a heavy pre-sales role and would make the help system a part of the demo. I am pretty sure everyone saw high value there.
And talk about complex, with depth, subtlety! That program demands more than mere buttons can deliver!
That concern won't apply everywhere, but it's worth keeping in mind. Even when my interactions with a simple menu are recorded (for analytics/profit) and reported the amount of data they get is at least limited.
I would not be surprised if newer fighter interfaces are already customized for the pilot in this way.
Speed: Search-based puts a floor on how fast an interaction can be. "Button Syndrome" interfaces are a slow "hunt and peck" for new users, but experienced users can use them extremely fast, building up muscle memory so they don't even need to consciously think about the action they're taking. Imagine piloting an F35 with a search-based interface.
Discoverability: Buttons make it explicit what functionality is offered by the product... somewhat. Users may not know exactly what a button does, but they can make an educated guess based on labeling and context, and it gives them a jumping off point to experiment with it or find it in the documentation. With search-base interfaces, there's no natural way for a user to discover functionality they aren't aware of. Worse, a user may remember a function exists but forget the terminology, flailing in the search box guessing different terms.
This is not to say search-based interfaces are bad. There are mitigations to the downsides (the article mentions a few, like search suggestions), plenty of upsides to go along with it, and let's not pretend that button-based interfaces are all sunshine and rainbows. I only mean to say that these are things that should be considered.
I think the broader takeaway of the article is: Always be thinking holistically. It's important to consider how your users interact with your product as a whole, not just the individual features. Also important to consider how different users of varying experience with the product and the domain will feel with the UI—Often features for "power users" come at the expense of new users or vice versa.