When someone reacts so negatively to material design that they won't use it, that is a failure. There's no matter of opinion there. The purpose of the design work is to make it usable.
No it cannot. First, because nobody cares about the goals of the designer -- it's all about the goals and satisfaction of the users.
(E.g. if the designer is in love with themselves and find everything they do great, then any crap design they've made that they're fine with, can be said to "satisfy their goals" and by this logic is "objectively good").
If you meant "satisfies the designer's stated goals when it comes to actual use" (e.g. make the UI intuitive, convenient, powerful, etc") then notice how all those words are still subjective, and the various hard objective design laws (Fitts law, etc) are not enough to cover the entirety of a design.
And of course all those are about the UX. A design can have great UX but still look like crap in the aesthetics department -- and this is also quite subjective.
>When someone reacts so negatively to material design that they won't use it, that is a failure. There's no matter of opinion there.
That's (someone's rejection) is the definition of subjective though.
So much for "design success is objective". If you meant "refusal to use can be objectively measured" sure, but that doesn't say much about the design.
Said person could be a bizarro outlier that prefers some way worse design for example.
But, what if I like/dislike the designers goals? In other words, if the designer painstakingly crafts a detail I don't care about, does it mean it is a good design?
Not trying to prove any point. Just trying to understand your perspective.
If that detail helps them achieve their desired business outcomes, then yes. You might not like the product, but the design work is good. If you are trying to weed your garden, a Tesla is not useful to you. That doesn't mean it's a bad design, it just wasn't designed for that particular need.
All design comes from a specific set of values, and can only be evaluated within the context of those values. The notion of universal design is a fiction. It's the remnant of the colonialist mindset, where there is a presumption of universal values.
I would agree that I don't prefer Material design. It feels, to me, too much of a lowest-common-denominator.
While I wouldn't use it, if I feel frustrated or find usage unpalatable, that to me is an indicator of inferior design.
And even at that, parent goes for a controversial, "if it fits the goals of the artist it is fine" view of art, which is hardly some universally accepted standard for art.
This is a pretty subjective statement. It seems that a lot of Duarte's designs are somewhat derivative. Material extends MS's Flat design. I'm also not sure how much of that is Duarte, its a pretty open secret that Google makes use of some pretty high end digital agencies who aren't allowed to let folks know what they're working on.
WebOS was pretty tacky though an interesting OS design - actually implemented better by LG on their SmartTVs.
The Sidekick may have been his most interesting product but it was completely broadsided by the release of the iPhone and was n't anywhere near competitive to the Blackberry so I'm not sure how innovative it was.
If anything Duarte's had pretty good record for working on products with innovative features but never necessarily ground breaking on UI/UX
I've got to stop you there. WebOS was far ahead of its time, and especially considered in the context of a small startup going against established players, was brilliant.
It offered in some ways better and more intuitive usability than iOS, along with a great app development ecosystem and philosophy.
Palm's WebOS devices were a pleasure to use, in a time when that was a very rare thing for a mobile device.
It was clunky under the hood and never received enough love. It would have been interesting to see where WebOS (phone) would be today had Palm survived.
Stuff like Xposed is interesting, but I haven't seen any software for mobile that managed to match the kind of community driven tweaking that Preware fostered.
I see this any time WebOS is mentioned but this makes WebOS sound a lot more innovative than it was. WebOS is widely lauded for two things: (1) the card application interface and (2) the accompanying physics/gestures, especially swipe from edge. Now these are great and appropriately lauded but that is a short list that really pales compared to a similar list of things the iPhone OS had introduced at that time. Other than that WebOS is basically a nicely polished clone of the iPhone OS. Even the cards metaphor itself, the hallmark of WebOS, was used two years earlier in the original iPhone in Mobile Safari and Cover Flow.
Like what?
Don't see much credit for that original work being passed around, but I haven't dug up the facts.
I liked the WindowsPhone 8 instance, pity that's being flushed away. Hope it will be stolen and resold to the public.
All UX/UI design on major platforms is "derivative". None is ground breaking.
I find it funny how you back up your claim by showing an equally derivative work (LG Smart TV)
Apps that follow it will all have a similar look and feel on a platform... however, you can still make both good and bad UIs within that (or any other) framework. It doesn't alleviate the need to work with a UI designer.
There are certainly a fair number of developers who will just download a Material-styled template. But please don't assume that you can't do much more.
Take a look at some of the showcase designs on the Material Design Lite site for examples: https://getmdl.io/showcase/index.html
What does that mean?
I get that opinion. But allow me to play the devil's advocate:
Mobile interfaces are small and restrictive. Touch screens and gestures have zero discoverability. Interfaces must scale to a multitude of different screen sizes and resolutions. Flare hurts usability in these situations. When designers break convention it is far more likely to result in confusion or frustration by end users. Well defined standards can enable me to use your app without even looking at the screen and drastically improve accessibility for things like screen readers.
I think the tendency toward flare stems from design education that emphasizes print media and tries to make a direct translation into Web/UX Design. Print media, and advertisements are meant to grab your attention, establish unique brand design language and brand identity. But If I'm already on your website or using your app you already have my attention. You've already sold me. Now simply help me accomplish the task I am here for in the least painful way possilbe. Branching out beyond common guidelines and creating new interface conventions may scratch your creative itch but it is rarely more efficient or easy to use that established conventions.
Coming from someone who WANTS to love android for philosophical reasons and bought the google nexus, google nexus 5x. I always went back to iphone. The biggest issue is the device is not very good in comparison to the current gen iphone. It feels 1-2 gen behind in performance.
I still use a first generation Nexus 5. SNES/N64/PSP emulators run like a dream. Apps open/transition instantly.
What performance metric are you even using?
When Android stutters, you can put money on it being down to the garbage collector running at an inopportune moment. This is the downside of most Android apps being built in Java, whereas most iOS apps are written in Objective C, which uses reference counting and so you have more deterministic release of allocated memory. The upside of this is little or no stuttering, but the downside is that you can still end up with pauses, but they can be in places which are hidden from the user. The other downside of GC is that developers can lean on it a bit more than is justifiable to create needless duplicates of objects on the assumption that they'll be garbage collected eventually... which can lead to GC stutter. A lot of Android's 'slowness' issues would go away if devs were a bit more careful with how they allocate their objects.
Another thing that makes Android seem slower than iOS is that Android gives apps a pretty lengthy grace period when they hang for some reason and will alert the user if it thinks the app has hung. iOS, OTOH, is less tolerant of this kind of thing and will just kill the offending app and rely on the app to restore its state when restarted. This hides a lot of issues with apps on iOS that are more obvious on Android. Which choice is better is a matter of debate: the iOS route gives the better user experience 90% of the time, but when you want that 10%, you really want that 10%.
Emulators (and quite a lot of games too) tend to be written in C and C++, which means they do manual memory management or use the conservative Boehm GC, so you end up with little or no GC stutter. OTOH, if the developer isn't careful, you're more likely to end up with memory leaks.
> Good for you, but please don't even try to convince anyone of the super performance of your favourite phone
...maybe take your own advice?
Apple's leadership in UI design the last couple of years has been a little lackluster. While they seem to be able to iterate, with a few missteps, I'm less sure about their capability to get a whole revamp done right.
The talent is surely there but the question is whether the leadership and willing to take the right risks is. It's going to be interesting going forward, I'm guessing they will have to introduce something widget/tile -ish in the next phone
Why? It is easy, intuitive, and used by millions of people.
Change for changes sake?
No wonder there is such a divide among users. I don't think age has anything to do with it though.
On Windows (and macOS) the desktop is fundamentally different, used differently, and is often obscured by your windowed content.
Luckly they managed to at least let users hide that in iOS10, but it's still a cesspool of rarely used apps.
Put another way.. You're manually 'fixing' the iOS UX to operate like the Android "default"?
Notifications are great for things that need your attention but the home screen becomes a little more of a seredipious view of app information that can increase the usefulness and engagement with an app
I would love to see the iPad interface evolve a bit and not look so much like my phone. I don't feel like they are using all that space as elegantly as they could be.
I don't think it has anything to do with hardware, they can be engineered in such a way they don't needlessly drain the battery, nor do I think most people would feel it was useless. Then again, people sometimes don't miss something before they have it :)
I had to help a friend to find a qrcode app on Sunday. Look for qrcode in the store, 842 found. Wow... None of them has a review or stars. How do you trust them? We kept scrolling for a while, nothing. Compare that with the Google store. It doesn't tell me how many qrcode apps are there but it gives me a rating for every single one. Then it's the usual hunt for the app with no ads and least permissions, but that's the same on the iPhone.
As for the store, well, the App Store actually has standards and minimums for apps and reviews. I would think a google search for "best qrcode app ios" would yield better results than your strange method, but, hey, to each his own.
She was as clueless as me about the lack of stars. We looked for qrcode in the App store. This is what I would have done on my Android. She didn't suggest an alternative. A very basic iOS user?
The top result for me has over 800 reviews and ratings. The vast majority of them have at least some reviews.
Well, perhaps they can license Live Tiles from Microsoft. There are definitely things to like there, and Microsoft's certainly not using them on phones anymore - at least not as far as real-world usage can show.
Right. Anything can be accessed so quickly a home screen should be more contextual than static app icons.
Agreed, but with a slight nitpick - Duarte was hired to lead development on Palm's webOS designs. PalmOS was the aging predecessor.
I wouldn't say force click is a coup... it's like Android's menu button in the way it hides functionality and non-standard UX. Heaven knows what's going to happen if I trigger it random app. Google was wise enough to drop the Menu button in Android
Were hamburger buttons an Android thing? I noticed them everywhere, including on the web.
More of a Twitter Bootstrap thing, I think.
With the Sidekick, PalmOS, and then Material Design, Matías Duarte has been consistently at the forefront of mobile UI design.
Jony Ive is probably the most brilliant consumer electronics hardware designer in the world, but I have yet to see any indication that he has any idea how to lead a platform UI design project. I had issues with Scott Forstall's style, but he was at least leading the charge somewhere.
In my opinion, force click, Siri, 3D wallpapers, etc, have not been major coups in terms of UI finesse. At best Apple is in a holding pattern right now, I haven't seen any indication that they're pushing the state of the art outside of the hardware. The animations keep getting flashier and smoother, but that's not really UI design.
I thought Ive's strong understanding of design methodology would be enough, but I think maybe software design requires a different way of thinking. I don't know.