Interactive documents v websites. What research/studies exist to cover when one should be used over the other?

by Monomeeth   Last Updated April 24, 2016 08:06 AM

In discussing my question Does any research/study exist on what makes an interactive document better from a user experience perspective? an interesting argument has arisen that using a website is a better approach for creating an interactive document, as opposed to creating an interactive PDF for example.

To my mind, an interactive document is not the same as a website. Sure, they can be designed to be very similar and can share some of the same attributes and goals, but a single document that is entirely portable and can be viewed on any computer regardless of whether it is online or not will meet the needs of many situations that a website cannot do in the same way or with the same ease.

Some examples I can think of where creating interactive documents (such as PDF) may be preferable:

  • for organisations that have staff on the road without easy access to the internet
  • in situations where the content is commercial-in-confidence or has some other type of security restriction on it
  • where ensuring that what is viewed appears exactly as intended (although the interactivity may not always work as intended on some devices)
  • to ensure that when it is printed it prints as intended (incl. the ability to prevent printing altogether)
  • to ensure maximum portability
  • to minimise the risk of these documents being blocked by "email" and "internet" gateways
  • for archival/legal purposes where ensuring that an accurate historical record needs to be kept of the entire document without fear that images and other interdependent files have changed or been deleted

The above are only some examples.

I know an argument could be put forward that you can create a website that is stored locally (and not in fact published online at all), but the portability of these is questionable. For example, one can email a single PDF while one cannot email a website. Sure, you could compress the site (e.g. into .zip format) but many email gateways will block compressed archives.

So, I am wondering what research or studies exist relating to the comparison of interactive documents with websites from a user experience perspective, and in what situation(s) should one choose either option over the other to ensure the best experience for users.



Answers 1


This question is a false dichotomy from implementation point of view and the UX questions are unrelated to which implementation is chosen (if done well), so it is very unlikely that any such research exists:

  • *.pdf, *.docx, *.odt and other "document" formats can and often do contain non-portable content, e.g. links to dead sites, embedded videos/pictures without codecs (assuming the format will be supported by the OS/apps in 20 years or not needed in 20 years)
  • "websites" format - html+css+javascript+base64-encoded-binary-data can be stored as single offline file format (a proprietary web archive *.mht format in Internet Explorer already exists and it can be replicated in cross-browser-compatible *.html - see e.g. http://stackoverflow.com/questions/1207190/embedding-base64-images)
Aprillion
Aprillion
April 24, 2016 07:29 AM

Related Questions


Survey with many optional questions

Updated May 15, 2017 18:16 PM

Should I keep my website logo always visible?

Updated March 14, 2017 03:16 AM

Options for card layout on website

Updated August 02, 2017 14:16 PM

split screen layout pros and cons

Updated March 28, 2015 06:05 AM