UX teams at Microsoft, Google and Apple started this downward trend. Junk slowly destroyed our multidimensional interactions by hiding options from our (or, should I say "their") property by removing a visual dimension at a time.
We're devolving from the already-poor web3.0 husks of Menus, Toolbars, and local help files so revered in the eighties and nineties to a place where none of them exist even when a screen is present (your phone is less and less likely to have physical buttons so when on fullscreen you end up pixel hunting, long-pressing the screen looking for hidden popup menus, and quitting a program because settings option only appears from certain hidden contexts... )
So now it's common for the only option to be a blank screen with an ill-placed hamburger menu and minimal output and they're killing even that.* We've fallen a long way down from the days when a rich menu had a Preferences entry that led to a dialog with a multiple rows of tabs.
The commercial world is basically hiding all help files, menus, toolbars and buttons behind a blackbox, offering screenless products that are forcing users to move their vocal cords to trigger little more functionality than a linear command-line. They're stepping back into the DOS days, except worse... those times used to gift us with keyboards and a screen, and obligatory user training on usage and error correction back then. You end up with situations like everyone slashdot who on this week's Google Home outage may have thought of visiting the store because the "Sorry, something went wrong" error for all commands and even involving local alarm clocks or casting. It's the ultimate blackbox-ification since the product is broken without the net (there was really no help or GUI indication of what to do, so it's not hard to empathize with the guy).
We now have the Pebble "smart" watch where the date/time menu makes it impossible to actually SET the date and time. When the device is discharged it resets to 12:00 of some obscure day. A watch with such a reasonable set of hardware buttons shouldn't have to be paired with an app on a phone just to tell it the time, man!
Chromecasts and Fitbits are worse, with no screens. I see more "convenient" Wifi features from printers and recent dedicated cameras that want to roam free on our home networks (along with IoT garbage and Windows 10 and our Sony smart tvs ) and demand installation of an always-on app. There used to be a time when we do a one-time wired setup where a CD installer took care of everything, and then some http maintenance config option would remain for convenience without having the company spy on you.
We even have this little-used WPS button that could get adapted precisely to get past the issue of inputting a Wifi password on a screenless device. Heck,
all bluetooth devices avoid the App trap by having a pairing button and a clear default pin... but no, people just want to plug something in, install an app that will snitch on them, and then be locked out of their verbal command line when the service hiccups.
* And like their Google map page does when you visit blocked scripts "When you have removed the javascript, what remains must be an empty page". Infuriating, considering 20 years ago the word ran maps oblivious to javascript settings, so this "must" is self-imposed, and with ill intentions knowning today's greed for analytics crimes.