Discussion:
[Design] Flat design makes users slower?
Corey Floyd
2017-09-05 22:32:35 UTC
Permalink
An interesting read


https://www.theregister.co.uk/2017/09/05/flat_uis_designs_are_22_per_cent_slower_official/
--
Corey Floyd
Engineering Manager
Readers
Wikimedia Foundation
***@wikimedia.org
Ryan Kaldari
2017-09-05 22:42:00 UTC
Permalink
Personally, I can't wait for the flat design fad to die in a flaming
inferno. Maybe then, I'll finally be able to tell if the caps lock on my
iPhone is on or not :)
Post by Corey Floyd
An interesting read

https://www.theregister.co.uk/2017/09/05/flat_uis_designs_
are_22_per_cent_slower_official/
--
Corey Floyd
Engineering Manager
Readers
Wikimedia Foundation
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
Chris Koerner
2017-09-06 13:54:57 UTC
Permalink
Ryan,
Caps lock is both on and off. It's Schrödinger's Caps.

(I'll see myself out)

Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
Post by Ryan Kaldari
Personally, I can't wait for the flat design fad to die in a flaming
inferno. Maybe then, I'll finally be able to tell if the caps lock on my
iPhone is on or not :)
Post by Corey Floyd
An interesting read

https://www.theregister.co.uk/2017/09/05/flat_uis_designs_ar
e_22_per_cent_slower_official/
--
Corey Floyd
Engineering Manager
Readers
Wikimedia Foundation
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
_______________________________________________
reading-wmf mailing list
https://lists.wikimedia.org/mailman/listinfo/reading-wmf
Federico Leva (Nemo)
2017-09-06 06:42:38 UTC
Permalink
Funny how it can take 5 years to realise something like this; maybe
"revenue" is the key. Microsoft didn't earn significant revenue from
user clicks on its interface in 2012 and was left clueless?

Yet it shouldn't be too hard to notice a 20 % slowdown with small
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such
big gap anywhere.

Would eye tracking be needed too?
https://www.usability.gov/how-to-and-tools/methods/eye-tracking.html
I've not read much on the topic, just this and little else:
http://www.ep.liu.se/ecp/101/004/ecp13101004.pdf
The only mention I see on the wiki is from Dario in 2012:
<https://www.mediawiki.org/wiki/Wikimedia_Features_engineering/Notes/2012-W07#Dario>

I don't remember if Abigail Ripstra was doing something of this kind.

Nemo
Jan Dittrich
2017-09-06 07:34:55 UTC
Permalink
Post by Federico Leva (Nemo)
Funny how it can take 5 years to realise something like this
Nielsen/Norman was critical towards it before (e.g.
https://www.nngroup.com/articles/flat-design/?lm=flat-design-best-practices&pt=article)
and I assume that one could find earlier articles on the problems of it.
Flat design often clashes with the well established idea of
signifiers/affordances.

Some of it's problems I see in OOUI, too (it is not unsolvable, just not
as robust as the "old style" 2.5D buttons)

Jan
Post by Federico Leva (Nemo)
Funny how it can take 5 years to realise something like this; maybe
"revenue" is the key. Microsoft didn't earn significant revenue from user
clicks on its interface in 2012 and was left clueless?
Yet it shouldn't be too hard to notice a 20 % slowdown with small
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such big
gap anywhere.
Would eye tracking be needed too?
https://www.usability.gov/how-to-and-tools/methods/eye-tracking.html
http://www.ep.liu.se/ecp/101/004/ecp13101004.pdf
<https://www.mediawiki.org/wiki/Wikimedia_Features_engineeri
ng/Notes/2012-W07#Dario>
I don't remember if Abigail Ripstra was doing something of this kind.
Nemo
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Jan Dittrich
UX Design/ User Research

Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
http://wikimedia.de

Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnÃŒtzig anerkannt durch das Finanzamt fÃŒr
Körperschaften I Berlin, Steuernummer 27/029/42207.
Bartosz Dziewoński
2017-09-06 10:22:31 UTC
Permalink
OOUI was originally created with a classic design for buttons and other
fields, and that theme (now called 'Apex') is still available and
maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex We
could switch to it at a moment's notice. Personally I wouldn't mind seeing
it again ;)

Still, buttons in the default theme are not entirely "flat", they have at
least borders (or strong backgrounds) to distinguish them. The biggest
problem is the existence of 'frameless' buttons (in both themes), which
look just like normal text if they don't have an icon or something.
--
Bartosz Dziewoński
Saint Johann
2017-09-06 14:58:22 UTC
Permalink
In all fairness, I hope we wouldn’t. OOUI has so much more elements that
have no alternative in Apex theme, even accessible checkboxes are not
present in Apex (see https://phabricator.wikimedia.org/T162849).
Retiring Apex, not reinstating it, seems like the best solution at this
point, since Wikimedia developers and designers have a pretty average
track record when it comes to consistent development of alternative
solutions (e. g., current skins).

The research itself is a bit misleading and sensationalising: it doesn’t
compare stylistic elements of flat design and skeuomorphism, it
essentially compares bad design practices (bad styling of CTA/primary
button, styling tabs like some kind of buttons, styling links like text)
and good practices. It should not be taken at word, although usually
Nielsen Norman Group have good points in their studies.
Post by Bartosz Dziewoński
OOUI was originally created with a classic design for buttons and
other fields, and that theme (now called 'Apex') is still available
and maintained.
https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex We could
switch to it at a moment's notice. Personally I wouldn't mind seeing
it again ;)
Still, buttons in the default theme are not entirely "flat", they have
at least borders (or strong backgrounds) to distinguish them. The
biggest problem is the existence of 'frameless' buttons (in both
themes), which look just like normal text if they don't have an icon
or something.
Pau Giner
2017-09-07 08:46:31 UTC
Permalink
Post by Federico Leva (Nemo)
Yet it shouldn't be too hard to notice a 20 % slowdown with small
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such big
gap anywhere.
For the case of Recent Changes a before/after comparison
<Loading Image...>
does
not seem to suggest that the changes involved going flat. In the previous
state the filtering UI was a box with a flat lists of links and text, while
the new UI uses contrast and grouping to help users identify the different
elements.

If there is any particular aspect related to flatness that anyone thinks we
need to pay special attention to, feel free to share it and we can
incorporate it in future research. We have been doing different rounds of
research to test initial concepts
<https://commons.wikimedia.org/wiki/File:Editing_-_Recent_Changes_Filters_Rd1_Findings_2016.09-10.pdf>
, iterated ideas
<https://commons.wikimedia.org/wiki/File:Editing_-_RC_Extended_Filters_Usability_Testing_Deck_2017.06.pdf>
and the version available on beta
<https://commons.wikimedia.org/wiki/File:Contributors_-_RC_Filters_Integrated_%2B_Beta_Satisfaction_testing_deck_2017.07.pdf>.
The results suggest that users are able to identify more clearly which is
the current state of the filters and how to manipulate them with the new
approach.

In general, I think that labels such as "flat design" combine several
different aspects that makes it hard to make broad statements like flat
design being good or bad for all contexts. Talking about the impact on
choices for the clarity of affordances, contrast of elements, layout
approaches, etc. makes more sense to me. For example, the Nielsen/Norman
article
<https://www.nngroup.com/articles/flat-design/?lm=flat-design-best-practices&pt=article>
criticizes both skeumorphism (for resulting in "clunky interfaces") and
flat design (for the loss of clickability signifiers), but recommends what
they call "flat design 2.0" for incorporating signifiers based on our
intuition of phisics as Google's material does:

Early pseudo-3D GUIs and Steve-Jobs-esque skeuomorphism often produced
Post by Federico Leva (Nemo)
heavy, clunky interfaces. Scaling back from those excesses is good for
usability. But removing visual distinctions to produce fully flat designs
with no signifiers can be an equally bad extreme. Flat 2.0 provides an
opportunity for compromise — visual simplicity without sacrificing
signifiers.
In all fairness, I hope we wouldn’t. OOUI has so much more elements that
have no alternative in Apex theme, even accessible checkboxes are not
present in Apex (see https://phabricator.wikimedia.org/T162849). Retiring
Apex, not reinstating it, seems like the best solution at this point, since
Wikimedia developers and designers have a pretty average track record when
it comes to consistent development of alternative solutions (e. g., current
skins).
The research itself is a bit misleading and sensationalising: it doesn’t
compare stylistic elements of flat design and skeuomorphism, it essentially
compares bad design practices (bad styling of CTA/primary button, styling
tabs like some kind of buttons, styling links like text) and good
practices. It should not be taken at word, although usually Nielsen Norman
Group have good points in their studies.
Post by Bartosz Dziewoński
OOUI was originally created with a classic design for buttons and other
fields, and that theme (now called 'Apex') is still available and
maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex
We could switch to it at a moment's notice. Personally I wouldn't mind
seeing it again ;)
Still, buttons in the default theme are not entirely "flat", they have at
least borders (or strong backgrounds) to distinguish them. The biggest
problem is the existence of 'frameless' buttons (in both themes), which
look just like normal text if they don't have an icon or something.
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
Peter Coombe
2017-09-08 17:28:19 UTC
Permalink
For what it's worth, we've done quite a few tests with WMF fundraising
banners of skeuomorphic vs more flat designs, and didn't find any clear
differences in performance overall. We're now using OOUI styles which have
consistently performed well. I think they strike a nice balance between
"flatness/cleanness" and signifiers, plus it's nice to have consistency
with other parts of the site.
Post by Federico Leva (Nemo)
Yet it shouldn't be too hard to notice a 20 % slowdown with small
Post by Federico Leva (Nemo)
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such big
gap anywhere.
For the case of Recent Changes a before/after comparison
<https://phab.wmfusercontent.org/file/data/keh3ox7d7zowy776azjp/PHID-FILE-xyklxklkb6g7nyu3jmi2/RC-before-after.png> does
not seem to suggest that the changes involved going flat. In the previous
state the filtering UI was a box with a flat lists of links and text, while
the new UI uses contrast and grouping to help users identify the different
elements.
If there is any particular aspect related to flatness that anyone thinks
we need to pay special attention to, feel free to share it and we can
incorporate it in future research. We have been doing different rounds of
research to test initial concepts
<https://commons.wikimedia.org/wiki/File:Editing_-_Recent_Changes_Filters_Rd1_Findings_2016.09-10.pdf>
, iterated ideas
<https://commons.wikimedia.org/wiki/File:Editing_-_RC_Extended_Filters_Usability_Testing_Deck_2017.06.pdf>
and the version available on beta
<https://commons.wikimedia.org/wiki/File:Contributors_-_RC_Filters_Integrated_%2B_Beta_Satisfaction_testing_deck_2017.07.pdf>.
The results suggest that users are able to identify more clearly which is
the current state of the filters and how to manipulate them with the new
approach.
In general, I think that labels such as "flat design" combine several
different aspects that makes it hard to make broad statements like flat
design being good or bad for all contexts. Talking about the impact on
choices for the clarity of affordances, contrast of elements, layout
approaches, etc. makes more sense to me. For example, the Nielsen/Norman
article
<https://www.nngroup.com/articles/flat-design/?lm=flat-design-best-practices&pt=article>
criticizes both skeumorphism (for resulting in "clunky interfaces") and
flat design (for the loss of clickability signifiers), but recommends what
they call "flat design 2.0" for incorporating signifiers based on our
Early pseudo-3D GUIs and Steve-Jobs-esque skeuomorphism often produced
Post by Federico Leva (Nemo)
heavy, clunky interfaces. Scaling back from those excesses is good for
usability. But removing visual distinctions to produce fully flat designs
with no signifiers can be an equally bad extreme. Flat 2.0 provides an
opportunity for compromise — visual simplicity without sacrificing
signifiers.
In all fairness, I hope we wouldn’t. OOUI has so much more elements that
have no alternative in Apex theme, even accessible checkboxes are not
present in Apex (see https://phabricator.wikimedia.org/T162849).
Retiring Apex, not reinstating it, seems like the best solution at this
point, since Wikimedia developers and designers have a pretty average track
record when it comes to consistent development of alternative solutions (e.
g., current skins).
The research itself is a bit misleading and sensationalising: it doesn’t
compare stylistic elements of flat design and skeuomorphism, it essentially
compares bad design practices (bad styling of CTA/primary button, styling
tabs like some kind of buttons, styling links like text) and good
practices. It should not be taken at word, although usually Nielsen Norman
Group have good points in their studies.
Post by Bartosz Dziewoński
OOUI was originally created with a classic design for buttons and other
fields, and that theme (now called 'Apex') is still available and
maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex
We could switch to it at a moment's notice. Personally I wouldn't mind
seeing it again ;)
Still, buttons in the default theme are not entirely "flat", they have
at least borders (or strong backgrounds) to distinguish them. The biggest
problem is the existence of 'frameless' buttons (in both themes), which
look just like normal text if they don't have an icon or something.
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
n***@gmail.com
2017-09-18 19:00:36 UTC
Permalink
Not that I agree with either but just stumbled on a follow up post that
might be relevant
Post by Peter Coombe
For what it's worth, we've done quite a few tests with WMF fundraising
banners of skeuomorphic vs more flat designs, and didn't find any clear
differences in performance overall. We're now using OOUI styles which have
consistently performed well. I think they strike a nice balance between
"flatness/cleanness" and signifiers, plus it's nice to have consistency
with other parts of the site.
Post by Federico Leva (Nemo)
Yet it shouldn't be too hard to notice a 20 % slowdown with small
Post by Federico Leva (Nemo)
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such big
gap anywhere.
For the case of Recent Changes a before/after comparison
<https://phab.wmfusercontent.org/file/data/keh3ox7d7zowy776azjp/PHID-FILE-xyklxklkb6g7nyu3jmi2/RC-before-after.png> does
not seem to suggest that the changes involved going flat. In the previous
state the filtering UI was a box with a flat lists of links and text, while
the new UI uses contrast and grouping to help users identify the different
elements.
If there is any particular aspect related to flatness that anyone thinks
we need to pay special attention to, feel free to share it and we can
incorporate it in future research. We have been doing different rounds of
research to test initial concepts
<https://commons.wikimedia.org/wiki/File:Editing_-_Recent_Changes_Filters_Rd1_Findings_2016.09-10.pdf>
, iterated ideas
<https://commons.wikimedia.org/wiki/File:Editing_-_RC_Extended_Filters_Usability_Testing_Deck_2017.06.pdf>
and the version available on beta
<https://commons.wikimedia.org/wiki/File:Contributors_-_RC_Filters_Integrated_%2B_Beta_Satisfaction_testing_deck_2017.07.pdf>.
The results suggest that users are able to identify more clearly which is
the current state of the filters and how to manipulate them with the new
approach.
In general, I think that labels such as "flat design" combine several
different aspects that makes it hard to make broad statements like flat
design being good or bad for all contexts. Talking about the impact on
choices for the clarity of affordances, contrast of elements, layout
approaches, etc. makes more sense to me. For example, the Nielsen/Norman
article
<https://www.nngroup.com/articles/flat-design/?lm=flat-design-best-practices&pt=article>
criticizes both skeumorphism (for resulting in "clunky interfaces") and
flat design (for the loss of clickability signifiers), but recommends what
they call "flat design 2.0" for incorporating signifiers based on our
Early pseudo-3D GUIs and Steve-Jobs-esque skeuomorphism often produced
Post by Federico Leva (Nemo)
heavy, clunky interfaces. Scaling back from those excesses is good for
usability. But removing visual distinctions to produce fully flat designs
with no signifiers can be an equally bad extreme. Flat 2.0 provides an
opportunity for compromise — visual simplicity without sacrificing
signifiers.
In all fairness, I hope we wouldn’t. OOUI has so much more elements that
have no alternative in Apex theme, even accessible checkboxes are not
present in Apex (see https://phabricator.wikimedia.org/T162849).
Retiring Apex, not reinstating it, seems like the best solution at this
point, since Wikimedia developers and designers have a pretty average track
record when it comes to consistent development of alternative solutions (e.
g., current skins).
The research itself is a bit misleading and sensationalising: it doesn’t
compare stylistic elements of flat design and skeuomorphism, it essentially
compares bad design practices (bad styling of CTA/primary button, styling
tabs like some kind of buttons, styling links like text) and good
practices. It should not be taken at word, although usually Nielsen Norman
Group have good points in their studies.
Post by Bartosz Dziewoński
OOUI was originally created with a classic design for buttons and other
fields, and that theme (now called 'Apex') is still available and
maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex
We could switch to it at a moment's notice. Personally I wouldn't mind
seeing it again ;)
Still, buttons in the default theme are not entirely "flat", they have
at least borders (or strong backgrounds) to distinguish them. The biggest
problem is the existence of 'frameless' buttons (in both themes), which
look just like normal text if they don't have an icon or something.
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
Jonathan Morgan
2017-09-19 17:09:54 UTC
Permalink
Oh, thanks for sharing this Nirzar. And I DO agree with Sean Dexter: it
looks like most of these task scenarios compared "weak signifiers" and
"strong signifiers", of which the 'flatness' of the design element was not
the most salient difference. Not by a long shot.

I used Windows phone for a number of years. And to be fair many of the
signifiers in Metro *were* quite weak---for example, lots of clickable
textual elements were the same color as display text, and only visually
differentiated by their placement, font, size, etc.

I can certainly see how this makes a UI less easily *learnable. *I'm not
sure it makes the UI less *usable* overall, at least not for people who are
already somewhat familiar with it. A lot of NN's user testing is performed
in an e-Commerce context, and the scenarios implicitly or explicitly assume
the user is interacting with a new webpage or UI for the first time. Strong
signifiers are obviously important in that case.

I'm not sure they are always *quite *as important for applications that see
repeated use--like a launcher, a music . Once I know that clicking on
widget X causes Y to happen, does widget X really need to look like a big
red 3D button?

But then, I loved flat design, and still do. :)

For better or worse, most of us are pretty use to weak/absent signifiers in
a mobile context by now--think about all the functionality on your phone
that is only accessible through multitouch gestures, which usually aren't
called out in the UI *at all.*

- J
Post by n***@gmail.com
Not that I agree with either but just stumbled on a follow up post that
might be relevant
you-should-question-nielsen-normans-research-on-the-trendy-design-style-
39a991517e02
Post by Peter Coombe
For what it's worth, we've done quite a few tests with WMF fundraising
banners of skeuomorphic vs more flat designs, and didn't find any clear
differences in performance overall. We're now using OOUI styles which have
consistently performed well. I think they strike a nice balance between
"flatness/cleanness" and signifiers, plus it's nice to have consistency
with other parts of the site.
Post by Federico Leva (Nemo)
Yet it shouldn't be too hard to notice a 20 % slowdown with small
Post by Federico Leva (Nemo)
usability tests/focus groups. It could be interesting to test a couple
existing skins and a couple big interface changes in the works (such as
Special:RecentChanges and Special:Search) to see if there is any such big
gap anywhere.
For the case of Recent Changes a before/after comparison
<https://phab.wmfusercontent.org/file/data/keh3ox7d7zowy776azjp/PHID-FILE-xyklxklkb6g7nyu3jmi2/RC-before-after.png> does
not seem to suggest that the changes involved going flat. In the previous
state the filtering UI was a box with a flat lists of links and text, while
the new UI uses contrast and grouping to help users identify the different
elements.
If there is any particular aspect related to flatness that anyone thinks
we need to pay special attention to, feel free to share it and we can
incorporate it in future research. We have been doing different rounds of
research to test initial concepts
<https://commons.wikimedia.org/wiki/File:Editing_-_Recent_Changes_Filters_Rd1_Findings_2016.09-10.pdf>
, iterated ideas
<https://commons.wikimedia.org/wiki/File:Editing_-_RC_Extended_Filters_Usability_Testing_Deck_2017.06.pdf>
and the version available on beta
<https://commons.wikimedia.org/wiki/File:Contributors_-_RC_Filters_Integrated_%2B_Beta_Satisfaction_testing_deck_2017.07.pdf>.
The results suggest that users are able to identify more clearly which is
the current state of the filters and how to manipulate them with the new
approach.
In general, I think that labels such as "flat design" combine several
different aspects that makes it hard to make broad statements like flat
design being good or bad for all contexts. Talking about the impact on
choices for the clarity of affordances, contrast of elements, layout
approaches, etc. makes more sense to me. For example, the
Nielsen/Norman article
<https://www.nngroup.com/articles/flat-design/?lm=flat-design-best-practices&pt=article>
criticizes both skeumorphism (for resulting in "clunky interfaces") and
flat design (for the loss of clickability signifiers), but recommends what
they call "flat design 2.0" for incorporating signifiers based on our
Early pseudo-3D GUIs and Steve-Jobs-esque skeuomorphism often produced
Post by Federico Leva (Nemo)
heavy, clunky interfaces. Scaling back from those excesses is good for
usability. But removing visual distinctions to produce fully flat designs
with no signifiers can be an equally bad extreme. Flat 2.0 provides an
opportunity for compromise — visual simplicity without sacrificing
signifiers.
In all fairness, I hope we wouldn’t. OOUI has so much more elements
that have no alternative in Apex theme, even accessible checkboxes are not
present in Apex (see https://phabricator.wikimedia.org/T162849).
Retiring Apex, not reinstating it, seems like the best solution at this
point, since Wikimedia developers and designers have a pretty average track
record when it comes to consistent development of alternative solutions (e.
g., current skins).
The research itself is a bit misleading and sensationalising: it
doesn’t compare stylistic elements of flat design and skeuomorphism, it
essentially compares bad design practices (bad styling of CTA/primary
button, styling tabs like some kind of buttons, styling links like text)
and good practices. It should not be taken at word, although usually
Nielsen Norman Group have good points in their studies.
Post by Bartosz Dziewoński
OOUI was originally created with a classic design for buttons and
other fields, and that theme (now called 'Apex') is still available and
maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex
We could switch to it at a moment's notice. Personally I wouldn't mind
seeing it again ;)
Still, buttons in the default theme are not entirely "flat", they have
at least borders (or strong backgrounds) to distinguish them. The biggest
problem is the existence of 'frameless' buttons (in both themes), which
look just like normal text if they don't have an icon or something.
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
_______________________________________________
Design mailing list
https://lists.wikimedia.org/mailman/listinfo/design
--
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) <https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)>
jan dittrich
2017-09-20 07:29:19 UTC
Permalink
Hi, 
TL;DR: Not having visual redundancy makes UI brittle. 
And to be fair many of the signifiers in Metro were quite weak---for
example, lots of clickable textual elements were the same color as
display text, and only visually differentiated by their placement,
font, size, etc.
I assume this is partly due to flat design’s focus on a few graphical
dimensions. If you don't e.g. use shadows, 3D (or any other additional
dimension) there are few redundant fallbacks. And this is what worries
me about much flat design: With one very good designer it is probalby
all fine. But if many people design slightly incoherently with it
and/or make minor mistakes it gets harder to use. Highlighting elements
with color and/or bold text e.g. is a standard graphic design practice,
but now, if you make the highlight to small or a short text bold, it
becomes a fake-affordance-button.  So it is not that flat design is
wrong, it is very brittle. 
I can certainly see how this makes a UI less easily learnable.
I strongly think that most, if not all applications should be easily
learnable. Partly because everyone begins at some point and because
needing to rely on learned things still will have some background
cognitive load and proneness to errors. 
Jan
Oh, thanks for sharing this Nirzar. And I DO agree with Sean Dexter: it looks like most of these task scenarios compared "weak signifiers" and "strong signifiers", of which the 'flatness' of the design element was not the most salient difference. Not by a long shot.> > I used Windows phone for a number of years. And to be fair many of the signifiers in Metro were quite weak---for example, lots of clickable textual elements were the same color as display text, and only visually differentiated by their placement, font, size, etc.
I can certainly see how this makes a UI less easily learnable. I'm not sure it makes the UI less usable overall, at least not for people who are already somewhat familiar with it. A lot of NN's user testing is performed in an e-Commerce context, and the scenarios implicitly or explicitly assume the user is interacting with a new webpage or UI for the first time. Strong signifiers are obviously important in that case. 
I'm not sure they are always quite as important for applications that see repeated use--like a launcher, a music . Once I know that clicking on widget X causes Y to happen, does widget X really need to look like a big red 3D button?
But then, I loved flat design, and still do. :)> > For better or worse, most of us are pretty use to weak/absent signifiers in a mobile context by now--think about all the functionality on your phone that is only accessible through multitouch gestures, which usually aren't called out in the UI at all.
- J
Not that I agree with either but just stumbled on a follow up post that might be relevant 
For what it's worth, we've done quite a few tests with WMF fundraising banners of skeuomorphic vs more flat designs, and didn't find any clear differences in performance overall. We're now using OOUI styles which have consistently performed well. I think they strike a nice balance between "flatness/cleanness" and signifiers, plus it's nice to have consistency with other parts of the site.
Post by Pau Giner
Yet it shouldn't be too hard to notice a 20 % slowdown with small usability tests/focus groups. It could be interesting to test a couple existing skins and a couple big interface changes in the works (such as Special:RecentChanges and Special:Search) to see if there is any such big gap anywhere.> > > > > > > > For the case of Recent Changes a before/after comparison does not seem to suggest that the changes involved going flat. In the previous state the filtering UI was a box with a flat lists of links and text, while the new UI uses contrast and grouping to help users identify the different elements. 
If there is any particular aspect related to flatness that anyone thinks we need to pay special attention to, feel free to share it and we can incorporate it in future research. We have been doing different rounds of research to test initial concepts, iterated ideas and the version available on beta. The results suggest that users are able to identify more clearly which is the current state of the filters and how to manipulate them with the new approach.
Early pseudo-3D GUIs and Steve-Jobs-esque skeuomorphism often produced heavy, clunky interfaces. Scaling back from those excesses is good for usability. But removing visual distinctions to produce fully flat designs with no signifiers can be an equally bad extreme. Flat 2.0 provides an opportunity for compromise — visual simplicity without sacrificing signifiers.> > > >
In all fairness, I hope we wouldn’t. OOUI has so much more elements that have no alternative in Apex theme, even accessible checkboxes are not present in Apex (see https://phabricator.wikimedia.org/T162849). Retiring Apex, not reinstating it, seems like the best solution at this point, since Wikimedia developers and designers have a pretty average track record when it comes to consistent development of alternative solutions (e. g., current skins).
The research itself is a bit misleading and sensationalising: it doesn’t compare stylistic elements of flat design and skeuomorphism, it essentially compares bad design practices (bad styling of CTA/primary button, styling tabs like some kind of buttons, styling links like text) and good practices. It should not be taken at word, although usually Nielsen Norman Group have good points in their studies.
OOUI was originally created with a classic design for buttons and other fields, and that theme (now called 'Apex') is still available and maintained. https://doc.wikimedia.org/oojs-ui/master/demos/?theme=apex We could switch to it at a moment's notice. Personally I wouldn't mind seeing it again ;)
Still, buttons in the default theme are not entirely "flat", they have at least borders (or strong backgrounds) to distinguish them. The biggest problem is the existence of 'frameless' buttons (in both themes), which look just like normal text if they don't have an icon or something.
______________________________> > > > > _________________
Design mailing list
***@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
Post by Pau Giner
--
Pau Giner
Senior User Experience Designer
Wikimedia Foundation
______________________________> > > > _________________
Design mailing list
***@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
______________________________> > > _________________
Design mailing list
***@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
______________________________> > _________________
Design mailing list
***@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/design
--
Jonathan T. Morgan> Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF)
_______________________________________________
Design mailing list
***@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/design>
--
------------------------------------------------
Jan Dittrich
UX Design/
User Research

Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
http://wikimedia.de

Imagine a world, in which every single human being can freely share in the sum of all knowledge. That‘s our commitment.

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnÌtzig anerkannt durch das Finanzamt fÌr Körperschaften I Berlin, Steuernummer 27/029/42207.
Joel Aufrecht
2017-09-28 23:24:36 UTC
Permalink
​..​
. And this is what worries me about much flat design: With one very good
designer it is probalby all fine. B
​​
ut if many people design slightly incoherently with it and/or make minor
mistakes it gets harder to use.
​... So it is not that flat design is wrong, it is very brittle.
Here's a fresh example of flat design gone awry due to losing too many
cues. I am depositing a check via banking app. The first screenshot is at
the beginning. The second is after I've photographed the check front and
back and manually typed in the value. Can you see what to do next?


​
The button changes color when active, but it changes to look exactly like
the title, which is not clickable. And it's placed above the other
controls, rather than below them. So it's missing some key affordance cues
(look clickable; be in the expected place; be in sequence) and the one it
does have (change affordance from "visible but visibly not available" to
"visibly available") is botched. Some of that is due to flat design
reducing the margin of error.


I can certainly see how this makes a UI less easily learnable.
I strongly think that most, if not all applications should be easily
learnable. Partly because everyone begins at some point and because needing
to rely on learned things still will have some background cognitive load
and proneness to errors.
I think there may be such a thing as permanently unlearnable. Some users
can master certain apparently simple functions but not others that seem to
be as simple. The threshold of difficulty may vary by user. There are
functions and household controls and keyboard combinations that I never
master at the same level of muscle memory as others. Another example where
flat design contributes to a permanently unlearnable or less learnable
function:

Try to find the control to change from random play to linear play. One
For better or worse
​​
, most of us are pretty use to weak/absent signifiers in a mobile context
by now--think about all the functionality on your phone that is only
accessible through multitouch gestures, which usually aren't called out in
the UI *at all.*
While I haven't presented any quantitative data above, I suspect that
​"use[d] to weak/absent signifiers" is not the same as​ not impacted by
weak/absent signifiers.

--
​Joel​

Loading...