User interface issues regarding embedded PDFs

Question

Q.1. What are the advantages and disadvantages, from a usability standpoint, of embedding PDFs in a web page?

Q.2. In general, for the average computer user, which scenario provides the most "streamlined" experience?

Q.3. Would using cookies to remember the options substantially improve Scenario #2?

Scenario #1

1. User sets options.
2. User clicks a Report button.
3. PDF is sent as an attachment (to Save or Open).

Advantages

• The options don't get reset.

Disadvantages

• The PDF can obstruct the web page.
• The user might leave too many PDF windows open (slowing system performance).

Scenario #2

1. User sets options.
2. User clicks a Report button.
3. PDF is embedded in the page.
4. User clicks back and the options will have been reset (AJAX, no cookies).

Advantages

• The results appear immediately (no extra clicks).

Disadvantages

• Not all browsers support embedding PDFs (?).
• The web page (i.e., the Report button) disappears.

Thank you!

Answer 1

How about scenario #3?

1. User sets options.
2. User clicks a Report button.
3. PDF appears in an IFRAME embedded in the page.
4. options stay in place

This would combine the advantages of the two: The options won't be reset; There will be only one PDF instance open at any given time (except for power users with multiple tabs, but they have to know what they're doing.)

You could also offer a separate direct download for experienced users.

Answer 2

I think it would be best to avoid embedding the PDF at all. If this purpose is to preview the data on the report, would it be possible to display an image of the first page of the PDF? Alternatively, if the purpose is to preview the data in the PDF, it might be easier to display the data as HTML. Either way, I think it would be better to use HTML or images (which load faster and more consistently across browsers) to preview the PDF and then offer a download link.

Answer 3

I hate when a pdf opens in a browser window. But I'm one data point, and one that's probably not interesting to you. What you need to do is talk to your actual customers and ask them instead.

Without more details it's just too hard to say what is best for your specific application. Do users use your app 8 hours a day, or only 8 minutes a month? Do they typically have large screens? Small? Do they access the app via mobile devices? Is viewing the report their primary job activity, or is the report something they'll print and shove in a drawer? Answer these questions and the answer to your usability question will be easier to get.

The bottom line is, ask your users. If you can't, or the answer is indeterminate, give them both options and let them choose.

Answer 4

This is a question perfect for UX Exchange:

http://uxexchange.com/

To answer the question, I'd step back first. We're talking PDFs. The format, alone, is going to be causing usability and accessibility issues.

Keep in mind:

• not everyone uses acrobat reader
• not everyone uses pdf plugins
• not every browser supports pdf plugins

Bottom line, get it out of a PDF to begin with.

Otherwise, if the format is required, surrender to default rather than embed, IMHO. I'd do one of two things:

1) send it to the browser as a PDF (letting the browser settings decide what to do with it)

2) generate the PDF and then provide a link to it

Answer 5

Personally, I would recommend against the "button" approach and allow your users to decide what they want by simply presenting a link (e.g. <a href="...">link</a>) to a download without a Content-Disposition header with a prominent PDF "icon".

This will allow everyday users to either:

1. Left click the link and allow their browser preferences interpret the link as they normally do (be that in Adobe Reader in the browser, prompt for download, browser extension, etc).
2. Right click the link and choose to "Save As...". Perhaps a friendly div could appear when hovering over this link recommending to users that if they wish to download the PDF, they should right click and choose "Save As")

A form button (which is what I assume you are considering above) doesn't allow this right click option.

In my experience, people hate the "surprise" of a PDF opening in their browser without warning. Power-users are typically the ones most annoyed by this and have configured their browsers to handle this or are used to "right clicking" links to these kinds of files (when they know they are coming).