10

For most people, domain.com is as clear as www.domain.com, and so the preference depends on the designer (although I prefer domain.com) However, naked domains (i.e. domain.com) and the www version are not always synonymous. First make sure that the naked version works. Don't just use the naked version without first checking.


10

Give them a "print" option, rather than a "high res" option? Sounds like you might not be speaking your users' language. Also, how much of a pain is this really to users? Maybe there is a reason they save and print the low-res version, e.g., download times, or they worry that they won't get what they see. A simple usability test with a representative user ...


9

This is a common UX situation Most users 'self police' and do not need warnings or guidance. You have few heavy users who need to be [gently warned/dissuaded] to avoid waste or abuse. You have isolated cases of abusive users. This heavily skewed distribution of users is very common in lot of applications (cell phone usage, all you can eat buffets, Netflix ...


8

"http://domain.com" is unambiguously a website. "www.domain.com" is equally clear but technically not necessarily a website. "domain.com" is likely a website. "go.to" (Tongan TLD) is recognized by the internet savvy as a domain name and likely a website, but many people might miss that meaning. I'd be inclined to use "http://" or "www." as a prefix to ...


6

Have a rollover state right on the image with big letters superimposed that say Click To Download Print Version. Clicking that could either directly download a version in the browser, or more simple, open the high-res version in a new tab where they can right-click to save it. This way, you give them what they want in an obvious manner before then even get ...


5

how often are people printing pages outside of 8.5 x 11? I have never printed at 8.5 x 11. I assume this is a U.S. paper size and is in inches. I print at A4, it is the standard printer size in the UK. It is 210mm x 297mm. Don't try to assume what sizes people are printing at, instead make your print styles flexible enough to cater for everyone (...


5

The flow should be something like this. The user clicks on 'print list'. After that, he selects his options, just like a regular print setup. The user confirms and prints. Now, based on the comments I know the favourites have another function besides only selecting so I'm not suggesting a change to that. Here's how I would design the second step. See ...


4

Printing is an expensive operation, requiring lots of time, ink and paper, so it's generally a good idea to assure users that they're getting what they want and confirm they are printing the right document (this can be an issue if they're printing from a file view interface where they could easily click the wrong file). That suggests a case for a print ...


4

I think most people nowadays understand it by first-level domain name (i.e. .com or .net, etc) so I believe you may drop the www. part.


4

In the U.S., a few years ago when social media was starting to boom, advertisers would often display a logo and state something like "Find us on Facebook" in TV and print media. However they started to realize that fan pages and other non-official profiles made that confusing, so then they started displaying full URL's (i.e., www.facebook.com/CoolCompany) ...


3

Using www. or not in front of the domain could depend on your audience. To be safe, prepend the domain with www. so there is no doubt. I would recommend all lower-case for esthetics. I have made content for many large companies in the past involving their domain and so far there has been no exception to the domain being lower case (Europe, it may be ...


3

What you describe isn’t so much a print dialog as a fully-featured database querying, reporting, and dissemination tool. That’s a huge chunk of functionality. It’s perhaps half of what the users use the ERP app for (the other half being modifying the database content). It’s too much to squeeze into one dialog. I think you need to break it into pieces. There ...


3

It's usually best to follow popular convention. In my area, the print marketing materials I've seen almost always include the www and usually exclude the http/https protocol. Though, if space is an issue, I would expect most anyone with internet access to understand domain.com as well. And I can't think of a marketing scenario in which the protocol prefix ...


3

Formatting a page for printing is essential, since some of the user like to print a web page. One example of that is a cooking receipt just because the surrounding environment at the time of cooking isn't suitable for a Laptop or tablet. Technically speaking you need to specify a print CSS and possibly also a "Printer friendly version"-button. The button ...


3

I would add time of print as one of your columns, and make each column sortable. Also I would add a checkbox with the label view printed jobs or view print history. The display of printed history rows would have a different, more sublime color to distinct from actual jobs. That way the history jobs could be easily recognized even if columns were sorted by ...


3

Only if that's what they've asked for. From a usability perspective - There will be people who don't want the balance to be shown on screen. They could be stood their with their wife / girlfriend, and don't want them knowing just how much money they do / don't have. Also, there may be technical constraints too. To display the balance requires the ATM ...


3

I see two choices here represented by two buttons. However, in both options confirm appears, so confirm is not really an option as it appears in both. Therefore, it should be part of the compulsory flow not the optional flow. What is optional is either to print or to email the tickets , (I understand). Frankly, since the cost of sending an email is 0, get ...


2

"Thou shalt speak thy user's language" :) While "behind the scenes" it is just printing, your users are thinking in terms of converting a file to another format. I'm sure that even users who know to "print to PDF" can only identify it as "hmm, this has the word PDF, and there's nothing else with PDF, so this must be the one I need". So spare them a thought ...


2

I think you're trying to solve the wrong problem. The two button solution sounds like it's obvious and straight forward and pretty much what you'd expect. Rather than change the buttons and abuse your search facets, I would look into why you feel like you have too many buttons on the page and try to solve that problem. The reason your proposed solution with ...


2

Although you may loathe the print funtionality, it seems, for a medical piece of software anyway, printing would be one of the most needed use cases. Lots of medical fields still rely on paper imo. What I have used in the past, and seems to work well especially for report like printing that you seem to need, is a print mode of the page. Like Google Maps. ...


2

I would advise keeping the print button when displayed on mobile/tablet devices, you're assuming that when people print the screen from their devices that they want to get a paper version. It is possible to print to a pdf that saves to their local/cloud storage which is especially useful for booking confirmations, receipts etc. Obviously I can't tell you ...


2

There is nothing saying you shouldn't have a print button on your mobile website, but it is not necessary. The browser the user is visiting your site from has every capability to provide the print functionality the user is looking for. If the user does not see the need to print from their mobile device, they aren't going to care about having that capability. ...


2

Check the colours you use for the text and background using one of the online tools, e.g. http://www.456bereastreet.com/archive/200709/10_colour_contrast_checking_tools_to_improve_the_accessibility_of_your_design/


2

This forum is about User Experience (not programmer experience) so I will give you the best answer from the users perspective, regardless of whether it is "quite an effort to implement". The best experience for the user, is to have a page that prints perfectly without having to download a PDF, or open a new simpler web page. If the user is very likely to ...


2

If you are specific about using two separate CTA's then you can make slight changes to your current UI as indicated in below mock up. If no item is starred then you can keep that CTA link/button disabled. Although I feel NGAFD's approach is better. hence in that case you can keep single print drop down where in user can select appropriate options for ...


2

As a techie, http:// (or, I hope, https://) makes it unambiguous, but – from my (informal) experience – often isn't used in mainstream media. Trying to put myself in a non-techie's shoes, I think www. as a prefix is sufficiently associated with "the web" that most people will recognise it as a web-address, and so may be the best. However, unless someone ...


2

Could you use a web/globe icon? Something like:


2

Download or Print whichever works better.


2

I got inspired by this answer however I object with the placement of the button. In my opinion it should be placed on the right-hand side of the screen, like this: Why on the right-hand side, one may ask? From the layout I assume the target device is a handheld (smartphone) type. The facts are that somewhere between 70% and 95% of the humanity is right ...


2

Another option it worth to think of and try it, is to include a floating download button, it will remain all the way and it will take action for the screen you swipe to it. The floating button now became a used behavior even in IOS.


Only top voted, non community-wiki answers of a minimum length are eligible