He is an academic course-coordinator in a university. He is a very busy man who spends most of the day in front of his computer.
As Carlos goes on about his daily tasks, every half an hour or so he checks the time. Reasons vary:
How long has he got before the 11:00 meeting?
How long before lunch time?
How long has ...
Highjacking expected user flows is bad. If a user closes an app, they expect it to close, not start opening up other apps (even if it's just a browser). Beyond annoying, it can be perceived as untrustworthy. "Oh great, now if I want to open up an app by this developer they're going to keep trying to launch something else. Delete."
You could have an exit ...
Some modern design guidelines certainly disprefer persistently-visible scrollbars, but not all. For example, in the Material Design guide, for menus, if a menu is scrollable, it should show a scrollbar. In any case, if your content is scrollable, it should be clear from looking at it that it affords scrolling.
It's up to an individual designer or guideline ...
You're introducing two big problems right off the bat; breaking conventions and clashing styles. Don't forget that Apple and Microsoft have released different interface guidelines for their respective platforms :
Windows UX Guidelines and the OS X UX Guidelines.
Using conventions is important and helps users work in your app without thinking (Don't Make Me ...
From a user's perspective, don't hijack my browser!
Don't touch the other software on my computer unless you're making it clear what's about to happen, and I have the option to opt out or opt in.
Don't make any obstinate to remove or persistent changes to my computer unless you're clear in explaining and I'm clear in understanding about what is ...
As a mouse user, I abhor scrollable content that doesn't give me a view of and access to scroll bars.
The scroll bar is a control. It allows me to quickly navigate large pages no amount of finger-scrolling, scroll-wheeling, etc. can compare with. It also gives me more precision for most pages than my scroll-wheel.
The scroll bar gives me information. It ...
The proposal is horribly flawed!
There is a fundamental weakness in the author's design approach, which is he doesn't state what problem he's trying to solve. Instead, he just starts by sketching a "home-less" UI which he thinks will look cool....i.e he's starting with an imagined solution rather than trying to solve a problem.
By failing to properly ...
Relax. Don't be the next king of spam.
Generally speaking (and I know generalisations are super unpopular around here, so bear with me) you should not be thinking about the first time the user quits your game.
That's the first time they have had enough of your game, or are interrupted. These are not people ready to consider your other games.
After a ...
The users experience in your application should fit with the experience they have come to understand and work within in their chosen (or forced upon) OS. They have built laws and rules of interaction on that experience, for good or bad.
A major drawback with designing an app to look more like OS X UI than Windows 7 or Vista UI is that the overall look and ...
Since your UI does not work, and your users does not understand the generation - you need to automate the process. If there is an existing invoice, the pdf-file needs to be deleted from the folder as soon as something is changed on the order, then recreated as soon as the users prints it again.
Usually you don't send the invoice before the products have ...
What if you compare it to a download button on any website that downloads the pdf. You cant access the file server but have to click the download button in order to get your file and will always download the latest version.
In your situation, the only way to acces the pdf directory could be though the 'view/print' button. This button will show the directory ...
Desktop: You can use expand and scroll methods.
According to Material Design:
On desktop, card content can expand and scroll internally
Mobile: Don't use a scroll inside the card, instead expand it.
Card collections only scroll vertically.
Card content that exceeds the maximum card height is truncated and does not scroll, but the card can be ...
There is a clock on the desktop so that people can tell the time!
This is the same reason there is a clock on my mobile phone, wireless phone, oven, microwave oven, car, weather station and iPod. They have clocks because a clock is useful and easy to implement.
Indicating the caps lock is on is a design pattern used for passwords. When the passwords are hidden and every character is only represented by a dot, users might not know they're typing capitals where they shouldn't.
It's easy to overlook the fact your caps lock is on. For example, I'm used to typing with ten fingers. While typing my elbows are set quite ...
You're asking about bundling ads with your game. Tread carefully. Software that opens a web browser to an advertisement, without the user's consent, is called adware, and it's universally hated.
It's perfectly fine to want people to be aware of your other games, but bundling adware with your software is not the way to do it. I've seen some games that "...
Simply put: DO NOT USE TABS.
This is not what tabs are meant for, so just use the box you have. Once the user selects the type, show the fields you have in second tab, only that right below the select field you have in first box. Basically: use only one box and get rid of tabs , then the "abstract type" will render no use at all, ergo problem solved, type ...
This viewpoint comes primarily from the Mac environment, where scrollbars are typically displayed briefly when content first appears, then fade out. When scrolling occurs (user triggered or otherwise), the scroll bar reappears. Only the handle is visible (as a semi-transparent rounded black bar); no arrows or gutter. If the cursor is over the scroll bar when ...
The guidelines for Windows 8 desktop applications are the same as for Windows 7.
That means that you'll find them here:
Windows 8 has two separate UIs: Windows Store apps (formerly known as "Metro-style apps") and Desktop.
Windows Store apps is the new, future oriented touch UI. ...
They are distinct:
OK: Applies the changes and closes the dialog (or goes back to the previous location / one level up)
Apply: Applies the changes so the user can see / work with the results, but keeps the dialog open, ready for further modifications
Cancel: closes the dialog without applying any changes.
The "Close button" in the window title usually acts ...
The desktop clock, or for that matter even the calendar, are primarily meant as a reflection of the date/time that the system is currently following.
The user of the system obviously knows the date/time (from his own watch or phone or otherwise), but he also expects to be reassured that the system he's working on is following the same date/time. For ...
While there are some blogs that cover a bit of this stuff, I think the best way to keep on top of it is to read the blogs and case studies covering the products themselves.
For Photoshop, John Nack's blog is the best place to go. He's the Principal Product Manager for Photoshop at Adobe and often talks about some of the problems they face.
For Windows, ...
It sounds like you've got a decision to make: Are you maintaining a folder of PDFs for the users to directly access, or are you not?
If you are not, and this is an example of users discovering an unintended shortcut around your planned workflow, then I'd suggest making it impossible for users to do this. Use a different file format, put your PDFs in an ...
Common patterns to indicate draggability:
This goes towards affordance. Users need to be able to recognize something can be dragged just by looking at it. A "grippy surface" is a common metaphor for this.
A grab-hand makes sense as well as the arrows (move) cursor. Currently grab is Webkit-only. Also note that some devices don't have a ...
download bmml source – Wireframes created with Balsamiq Mockups
How about this?
Just replace the checkboxes with radio buttons.
Color channel - selecting Lossless disables the slider, and selecting Lossy enables it.
Alpha channel - selecting Lossless sets the slider to 100% and selecting Lossy and setting it to 100% manually doesn't affect the ...
The following are a list of sites I visit weekly to see what's up and new. It is a mix of design, graphics, UX, resources. Their strength comes from following links in their articles, opening to door to more resources.
Spends half an hour searching for the product.
Finally finds it. Downloads it. Low bandwidth: it takes 10 minutes.
Installs/starts it. ("Oh! I downloaded a downloader, not the application! Where is the difference anyway?")
The downloader downloads. Low bandwidth: it takes another 40 minutes.
The application installs itself.
Result: The user ...
Generalising between platforms I would go with the following basic guidelines, they further emphasise a disabled field with a grey background.
Normal (with a value)
Black text, white background, black border.
Normal (with a placeholder)
Grey text, white background, black border.
Grey text, slightly lighter grey bg, grey border.
For the purpose of reducing visual chaos, I think you need a different kind of grid. I don’t think the issue is dividing the page into the right size of little equally sized rectangles. Rather, it’s the division of the page into a small number of large rectangles neatly laid out for the eye to scan. These rectangles are not necessarily all the same size, nor ...
To expand on Devin's point ...
Make the change obvious
Tabs mask the state change, asking users to know what you want without the help of visual cues. When an interaction changes the state of some other thing, make that change self-evident. In this case, changing the first control should pop the additional controls immediately into view (a little animation ...