I am researching the practice of communicating with a user what should he ought to do next while using your webapp. This is a great example ...
I'm working on a web-based reporting system that allows users to create ad-hoc charts. The user selects the data to be analyzed (e.g., sales dollars, sales volume, number of employees, etc.) in ...
This button should do what it looks like it should do. It opens a drop down of actions that a user can perform on their user account. Should I go with "Setting" or "Settings"?
The page for "help" within the site is designed well. The site totals about 40 questions, which has been reduced down from 86. My objective is to simplify the user experience for viewing/navigating ...
Basically, they can play around with the app, to get a feel for it in a advance. The target audience is business owners who may or may not (likely not) be technologically inclined. Demo implies that ...
Looking for an alternative to 'upgrade'. The problem is that in our web-app ui and communication, we are currently using two different versions of upgrade: the common upgrade/downgrade of the ...
Which makes for a better UX: using copy that is short and simple or copy that is casual, yet possibly more wordy?
In the context of a web app, which makes for a better User Experience: using copy that states the facts as simply as possible or copy that speaks in casual language, yet could end up being more wordy? ...
I am writing a little webapp, and am stuck on a UI hangup. I have a global menu bar at the top of the screen, that when the user is signed in consists of: Signed in as Joe User (with username as ...