On 6/9/2014 5:30 PM, J. Gomez wrote:
On Monday, June 09, 2014 11:12 PM [GMT+1=CET], Terry Zink wrote:
To repeat, UI/UX design is a specialty requiring extensive
training in cognitive, memory and attention psychology, testing
methodology and, oh yes, computer science.
So I guess we will wait until Apples just does it, and then go and
copy it, whichever side it falls.
Your response is tongue-in-cheek but I think represents a harsh
reality; only large companies have the resources to test UX'es and
the associated user behavior. For example, Amazon tests everything on
its webpage when it comes to pixel placement, and I believe that
Netflix does the same.
True, but at the same time UX is something that every user can talk about, as
per se every user has experience with it.
Every time I hear that UI is a black art to be refined only by ultra specialists, I
shiver in fear, because not only I have seen no improvement in that area since the
Windows 95 days (except perhaps the Windows 2000 cosmetic improvements), but on the
contrary what I have seen and *experienced* is plain user disgust. However, they call it
the product of deep field tests helped by teams of psychologists and what not, so that
"evolution" must be great and I be just wrong about it.
Good points.
Its a very complex subject.
How many different mail portals do you use/need as a user? How many
different mail portals does the service host offer, they need to
design for?
Vendors that have strategic control of the many integrated mail parts
have a better means of doing the things that you would to see. Make a
change here, comes with a change there. But sometimes these things
are split by product department, team, etc, so change doesn't always
come easy or fast.
The more you can single source your mail infrastructure, the better it
is and this has been happening more with long time established
systems. Centralization and a renewed direction towards online, with
full duplex interactive I/O is on the move, and it offer more
intelligent information to the end users.
I have at least 4-5 different MUA designs and thats hard to get right
with new stuff. Its also hard to change too. For example, Microsoft
recently (a few years now) abandoned their 20+ years of Newsgroups
NNTP servers and move their support operation to online forums. They
were already exploring with various UI look and feels for a few years
so now you have different competing support operations. When the MS
NNTP servers were turned off, to help support legacy NNTP news reader
users, like me, I wrote a NNTP proxy (Wildcat! Live Exchange,
http://opensite.winserver.com/wclex) with authenticated Live ID access
to the backend mail host using their SOAP protocol API wire. I did
it knowing it wasn't going to be a big thing as more and more people
went directly to the online forums. I can also control what the news
reader will display in the fields and also body by transforming the
extra data bits from the backend user and mail records; how many
brownie points the reader has, MVP, etc.
You are still using OE, thats old dude!! :) But sure, it works. I
have it on various machines. How do we change it to show the info
would like? Will you adapt to a new reader?
In the mean time, we have only the IETF protocols as a means to
communicate with each other, ideally, in a cooperative competitive
manner using global common methods, format and standards. It is
possible to put data bits in the 5322 headers. But its only good if
the MUA can use it.
It is still a good idea to extract general MUA ideas and offer them as
guidelines for the general MUA.
--
HLS
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
