How inconsistent design will save iTunes
teedot.com
How inconsistent design will save iTunes
1–10 of 24 posts
Re: How inconsistent design will save iTunes
#2Re: How inconsistent design will save iTunes
#3Which is a shame, really, because there aren't a whole lot of alternatives out there for OS X.
Re: How inconsistent design will save iTunes
#4Why not suggest a playlist with songs you listen to the most instead of making the searchbox bigger? Why not suggest songs to listen to next instead of hiding the genius bar?
Re: How inconsistent design will save iTunes
#5The idea of the growing search box is interesting, but what about one that kind of decays? It begins to shrink without usage until it reaches some point and then disappears. A good metaphor would be muscles, use them and they grow, don't lose them and they atrophy. I think non-IT oriented folk should be able to work out whats going on with enough visual cues. Especially if it becomes a common enough concept in software.
Edit: clarified a few things
Re: How inconsistent design will save iTunes
#6Re: How inconsistent design will save iTunes
#7This is like those dancing menus Office used to have, except even worse, because it lowers the discoverability of advanced functions just as you're getting to the stage where you'd be more likely to use them.
Re: How inconsistent design will save iTunes
#8Sorry, but this isn't a good idea. iTunes actually wouldn't be half bad if they permitted addons, theming and official support for MTP/MSC. However, inconsistant UI's are a big no-no according to the lecturer who taught me GUI design, because users have to continue learning and cannot rely on elements existing where they expect them.
Just my 2cents though.
Re: How inconsistent design will save iTunes
#9Microsoft Office used to have a UI that would do this. It was always the very first setting I'd change, disabling the feature. And Microsoft eventually discovered that it caused more confusion than it solved: people remembered seeing a command somewhere, but couldn't relocate it because it had been hidden.
Perhaps Microsoft's implementation could have been smarter, but I believe that they successfully demonstrated that this approach does not have merit.