So, this whole discussion about making clickable wireframes got me
thinking about something. As I'm working through my book,
interviewing a number of people from different backgrounds, I've come
across 5 different types, or purposes perhaps, for prototype:
1. As a common communication platform–using them to get everyone on
the same page, avoiding misinterpretation of ideas, using them as a
method to show and tell.
flanking my “vision” of a “latency-free world” , I'm interested in your assessment of the impact latency has on any user experience. I know that there is research showing that wait is a quite subjective thing, thus not necessarily having a negative impact, but what chances are there to raise more awareness for that issue?
This seems to be a never-ending discussion, regarding methods of
design and development. I contract to have certain system/apps that
I've designed prototyped, but certainly not all nor even the majority.
I work on wireframes, graphical layouts and keyframes, intensive
flows, and comprehensive implementation documentation, and have done
so for numerous OS GUIs (starting back in the 80s), lots of medical
equipment and devices, complex military systems, and so many mobile
device, phone, smartphone, and media players that I can't even count