While I feel quite confident with HTML and CSS, it seems to take a bit of
pain to use Dreamweaver for wireframing, perhaps because it tends to force
you into detail too early, when you are still on the "vision" stage of the
process, and feel like a WYSIWYG tool would be more appropriate.
On the other hand, wireframing in the WYSIWYG way entirely without HTML also
feels wrong, because first, the target medium is Web so it's closer to the
reality to think in HTML, and second, HTML is a powerful and expressive
language, and quite a mature one.
I am currently doing some research before I make a suggestion for how this
information should be displayed. Of the known formats I know that using
parenthesis () around the number or using the minus sign in front of the
number can be used. I have also seen both of these variations with the
numbers displaying in red.
I was just looking to get some feedback or possible resources that might
have more information or research that backs it one way or the other so I
can be more informed with this decision. Thank you for your feedback and
time in advance.
Title: Lead Interaction Designer
Location: San Francisco
Salary: 90's + bonus + stock options + outstanding vacation and benefits
An innovative, global financial institution is seeking a Lead
Interaction Designer with experience in Web applications, interaction
design, product development and usability. This is a unique opportunity
to join a small creative group with enormous influence in shaping one of
the most commonly used financial sites globally.
Our Marketing dep't wants me to do "usability testing" at an upcoming user conference -- a gathering of our software users. The conference's purpose: for users to improve their software skills and to learn about upcoming product advancements.
I proposed a card sort, because it's low-tech, relatively quick, and needs little setup. This meets y needs (I have something I need sorted), but does not meet the conference goals; it won't help users improve their skills or learn about upcoming product advancements. So it got lots of thumbs down.
Our client has recently merged with another large organization. Their
online/interactive presence has been compiled and there are issues with the
functionality of this large website. That is where you come in... we are
seeking a seasoned, talented usability consultant to work with cross
functional teams to identify current functionality and usability issues and
gather/create business requirements.
I am working to make the case to some of my company's IT professionals
that the decision to go with PDF delivery for certain reports rather
than HTML is a bad one.
I've read all of Nielson's articles on PDFs as well as rebuttals by
various individuals (where they only seem to point out that PDFs can do
more than just be for print; include hyperlinks, interactive forms, etc.
but not that they do these things well enough to remove usability
Can anyone else point me to statistics or reports on PDF vs. HTML and
PDF for onscreen reading.
We are working on a project that plans to start testing in Germany,
France, Spain, Austria and Belgium specifically and I was hoping to
get some good recommendations on usability recruiting firms in those
countries. Any assistance would be greatly appreciated. Thank you!
A new edition of the (in)famous Norwegian Bad Usability Calendar is
here. Check out the fresh examples of exaggerated use fancy of Web 2.0
design, cover flow, personalization, pull-down menus and more..
I am not sure whether this is the right forum, so sorry in advance if
not. But I saw some questions regarding eye tracking so I hope you
could help me. - BTW do you know forums that are completely dedicated
to eye tracking?
Okay, here is my challenge:
I am working since two years with eye tracking in the context of
dialogue systems. Currently I try to build a system which displays
information for several objects (e.g.
I'm running into an interesting conversation with more regularity
every week. That conversation surrounds the usability compromise that
sometimes occurs when optimizing pages, functionality, content
organization and linking strategies for search engines. There is
theory being preached within my company that if you optimize for
search engines, then you are optimizing for the user as well. I
disagree. I think they are two separate sets of logic, that may in
fact overlap, but are absolutely not in harmony.