The worst volume control user interfaces (2017)
1–10 of 20 posts
Re: The worst volume control user interfaces (2017)
#2Fun that you can post people’s gifs and images without attribution and make it the main body of your ‘content’
Re: The worst volume control user interfaces (2017)
#3The worst volume control? The one which utilizes a non-logarithmic function
Re: The worst volume control user interfaces (2017)
#4I feel like he's touching on a fact that we in software development and UI/UX design need to take heed; know when to stop.
Case in point: Google Maps. The old version used to not be as pretty but it worked really well. The new one looks fantastic. It's also slow, buggy, and not nearly as feature rich. Someone, somewhere inside the Google Maps team said, "We need to put out an update!" and nobody asked, "But, why?"
Re: The worst volume control user interfaces (2017)
#5Fun that you can post people’s gifs and images without attribution and make it the main body of your ‘content’
The guy should have licensed it from Conde Nast!?
Re: The worst volume control user interfaces (2017)
#6I feel like he's touching on a fact that we in software development and UI/UX design need to take heed; know when to stop. Case in point: Google Maps. The old version used to not be as pretty but it worked really well. The new one looks fantastic. It's also slow, buggy, and not nearly as feature rich. Someone, somewhere inside the Google Maps team said, "We need to put out an update!" and nobody asked, "But, why?"
Someone on all the Google design teams needs to stop hiding functionality behind ambiguous hamburger menus. Often they don’t even save any space or declutter the interface in any meaningful way. It’s extremely annoying and makes any useful setting or power-user function completely undiscoverable.
Re: The worst volume control user interfaces (2017)
#7I feel like he's touching on a fact that we in software development and UI/UX design need to take heed; know when to stop. Case in point: Google Maps. The old version used to not be as pretty but it worked really well. The new one looks fantastic. It's also slow, buggy, and not nearly as feature rich. Someone, somewhere inside the Google Maps team said, "We need to put out an update!" and nobody asked, "But, why?"
There's a brief commentary at the bottom of the OP in case anyone missed it.
My catchphrase with my kids: "just because you can doesn't mean you should".
Re: The worst volume control user interfaces (2017)
#8What about volume control UIs that are generally thought to be OK, but still drive you nuts? Has anyone else experienced this? Some years ago, when I made the questionable decision of buying a Das Keyboard, I was surprised by how much difficulty I had with the volume wheel that they put in the upper right corner. My prior keyboards had volume up and down buttons, and I never saw any problem or deficiency in that interface. But when I mentioned my frustration to a couple friends, they thought I was just being crotchety.
Re: The worst volume control user interfaces (2017)
#9After this started on reddit it spawned its own subreddit:
Re: The worst volume control user interfaces (2017)
#10I feel like he's touching on a fact that we in software development and UI/UX design need to take heed; know when to stop. Case in point: Google Maps. The old version used to not be as pretty but it worked really well. The new one looks fantastic. It's also slow, buggy, and not nearly as feature rich. Someone, somewhere inside the Google Maps team said, "We need to put out an update!" and nobody asked, "But, why?"
Like many google products, there's one or two basic features that I'd love to (re)enable to make the thing infinitely more usable for me, but which they simply refuse to.
With google maps it's the ability to enable scale all the time, not just showing scale briefly during zoom in/out changes.