Apple Music is way out of the normal density expected from a quality app. Apple has a phenomenal understanding of UI and they're one of the best - just look at the UI of the settings menu on your iPhone. Everything is cleanly laid out - just the right amount of information density. Apple Music seems like it was designed by someone like Will-I-Am (sorry :-) ) with absolutely zero understanding of basic functional UI principles.
If I were to design UI, I'd design it like how aviation does cockpits. Functional, not "trendy". Everything has a reason - if you can't explain "WHY", you shouldn't be designing UI. Personal taste, subjective opinions, "I kinda like it that way" doesn't work in aviation industry. Please don't take it as I mean Apple to follow the same principles, I am just mentioning the other end of the spectrum in UI design to provide contrast.
You seem to not understand the difference between designing UI for professional use where a user has to spend countless hours learning where each button is compared to an app for general population where users have to figure things out on their own.
Try to put an average joe into a jet cockpit, he would not understand a single thing, and he should NOT. You have to emphasize the most used features and elements with bigger font or negative white space in order for people to better understand where they should start and then walk their way into deeper understanding. In a fighter jet cockpit most of the buttons have identical look and it’s impossible to get started without reading a manual.
Everything you’re saying is absolutely true. UI design for masses is different than for a fighter pilot. I think Apple Music app is one of the worst even considering for the masses. Just look at their competitor - Spotify and learn from how they’ve designed for the masses. Apple Music arguably fails at meeting the basic UI expectations from a company, ironically, that values design immensely.
oh UI design in such an app always has a why
Before doing any modification on the UI of such an app, a lot of attention is given to user data.
It can't be completely objective because at the end of the day any interpretation of user data is at least a bit subjective (and generally way more than that). It does aim at being data driven though.
Again at some point there is a part of subjectivity in how you analyze the dataset.
It is still better than having no idea what your users are doing with your product.
Why is it that in some places there is a setting with a off/on toggle on the right, and in other places there is a setting that takes you to a sub-page with only a off/on toggle? For a current example, the Handoff menu under General.
While I agree they generally do a better than average job with UI, I've never really understood why the settings app has this inconsistency. It's been this way for many versions.
Rant over. Though not really a rant anyway, it doesn't make me mad, just puzzled.
For example, as you note, you have space to describe it and add possibly more UI to the feature. And in a future pass, you can decide to fold it back in to the existing UI and solidify it there. But that pass isn't necessarily worth it.
It isn't perfect, but it actually feels like an app designed to be used to play back music. Apple Music feels like a big, clunky, advertisement.
There is usually some degree of uniformity in streaming apps :
- all the services tend to get the same deals from the majors. Let's say service x gets terms A, service y will push to have the same A.
- they all solve the same problem .
Personally, I am not a big fan of spotify's UI :
- I despise Blur, it is the autotune of design and Spotify uses it a lot.
- As much as I like an app that is easier on my eyes without all these white areas everywhere, spotify is way too dark for my taste .
- it is surprisingly unpolished for such a big mobile team. To be fair a lot of the complexity is self imposed and comes from the fact that the UI is rendered based on the configuration sent by the server (display 3 columns of artists, etc)
Spotify does shine on the playback tech though. ogg vorbis, loudness equalization, etc they are on top of their game here.
I said it before and I'll say it again: Rdio knew. In my opinion the best streaming service for music enthusiasts and casual listeners alike.
Maybe I can shed _some_ light.
I worked for one of the big music streaming services for a while.
>limited valuable real estate on a mobile device.
Maximizing data density on a screen is absolutely not a goal on any 'large audience' app.
Yes, an app with tons of data crammed on a screen would make some folks happy in the HN/geeky communities (I am not sure that's true actually, but that's something that I often see power users asking for).
That's not who these apps are targeting though.
The design of these apps is often a mix between opinionated choices (basically what is trendy right now in the design circles) and what works in user testing.
Turns out, most of our users are ABSOLUTELY lost when they have to interact with a mobile app.
Music streaming services have way too many features :
albums playlists radios some kind of AI powered automatically created track lists (all services give this a different name, but they all have pretty much the same feature) lyrics, podcasts
On top of that, there is a ton of data for every single track : title album artist composer !!!! (classical music treatment is usually awful in any streaming app) . has lyrics ? is downloaded on your device ?
The player adds another layer of complexity : current track queue random mode repeat mode
Here is the dirty little secret of the music streaming industry : how to present all this in a way that allows random users (not geeks) to efficiently interact with the app : nobody knows how to do that :/ .
There is just way too many information to cram on a screen.
To pile on that, usual development cycles are focused on releasing new features, either to keep up with the competition or because that's how PMs demonstrate that they are 'improving' the app.
It is orthogonal to actually improving the user experience and we can see cycles of several years where the UI becomes more and more bloated with random stuff until designers are able to push a redesign with half of the features.
And soon we start cramming features again until the end of this new cycle.