Welcome to INLS 718. This is a course about the design of user interfaces, interactions, and experiences.

More notes...

• Granfield, M. (2016). A design by any other name would be so delightful. ACM Interactions Blog. \urlhttps://interactions.acm.org/blog/view/a-design-by-any-other-name-would-be-so-delightful. Retrieved from https://interactions.acm.org/blog/view/a-design-by-any-other-name-would-be-so-delightful
• Le Dantec, C. A. (2016). Design through collective action / collective action through design. Interactions, 24(1), 24–30. http://doi.org/10.1145/3018005
• Adams, J. L. (2001). Conceptual blockbusting: A guide to better ideas. Cambridge, Massachusetts: Perseus Publishing.
  • Read the following chapters in Conceptual Blockbusting:
  • 1 ("Introduction," pp. 1-14) and
  • 8 ("Groups," 159-174).

Today we will discuss the importance of collaboration in the design process. No design is every completed alone. The targets are too complex for this to be possible, but we often treat design as though it is something that starts and ends with one designer. We will attempt to reorient our thinking around this concept.

More notes...

⊕

Elliott Hauser is CEO of Trinket, a Royster fellow, SILS PhD student and MSIS alumnus. He has taught Programming for Information Professionals (INLS 560) and Tools for Information Literacy (INLS 161) at SILS. Elliott is a strong advocate for enabling students in any discipling to learn to code with as few barriers as possible.

Git - The Simple Guide (PDF) (WEB)

Hello World - GitHub Guides

The Ultimate Guide to Using Slack for Team Communication - The Huffington Post

How to revolutionize your team communication with Slack - WP Curve

Today we will have a crash course in using Git, GitHub, and Slack for collaboration. Elliott Hauser will join us to help get us up and running on GitHub and share insights about collaboration from his experience working on Trinket and integrating GitHub into his teaching practice. I recommend that you look over the above tutorials and cheat sheets before coming to class.

More notes...

• Roggema, R. (2014). The Design Charrette. In R. Roggema (Ed.), The Design Charrette: Ways to envision sustainable futures (pp. 15–34). Dordrecht, Netherlands: Springer Netherlands. http://doi.org/10.1007/978-94-007-7031-7_2
  • Read Chapter 2, "The Design Charette," pp. 15-34.
• Bias, R. G., Kortum, P., Sauro, J., & Gillan, D. (2013). Clothing the Naked Emperor: The Unfulfilled Promise of the Science of Usability. Interactions, 20(6), 72–77. http://doi.org/10.1145/2527299
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "80/20 Rule," p. 14,
  • "Design by Committee," p. 74, and
  • "Development Cycle," p. 78.

Today we will talk about planning a design process and ways to envision an uncertain future for the purpose of making decisions.

More notes...

Please read over (deep skim) the following tutorials under the "Alternative Paths" section here: Basic GNU Radio Usage for Signals

More notes...

• Miller, L. (2015). The Practitioner’s Guide To User Experience Design. New York: Grand Central Publishing.
  • Read Introduction and chapter 1, "Seeing through users' eyes," pp. 1-43.
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Accessibility," p. 16,
  • "Horror Vacui," p. 128,
  • "Mental Model," p. 154,
  • "Personas," p. 182.

More notes...

We're going to try today to set up environments so that we can start playing with hardware and looking at existing interfaces. Instructions for setting up VirtualBox and Kali Linux can be found in the notes below.

More notes...

Today we're going to do two things:

1. Make sure that we are all up and running with VirtualBox, Kali, and GNURadio.
2. Actually do a walk through with Erica and set up a receiver on our own devices.

Today we become the user. We'll want to keep some questions in mind as we do.

More notes...

Be sure to look again at the parts of Tuesday's readings for examples of user personas.

• Miller, L. (2015). The Practitioner’s Guide To User Experience Design. New York: Grand Central Publishing.
  • Heading: "Getting to know your users," pp. 20-29.
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • "Personas," p. 182.

We will analyze our self-observations from last time to create some personas for novice users.

More notes...

• Miller, L. (2015). The Practitioner’s Guide To User Experience Design. New York: Grand Central Publishing.
  • Read chapter 2, "Creativity Loves Constraints," pp. 44-69.
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Heirarchy," p. 122,
  • "Heirarchy of Needs," p. 124,
  • "Nudge," p. 172,
  • "Operant Conditioning," p. 174.

For the last few weeks we have been focused on users, and they will remain in our sphere of attention for the rest of the semester. This week, however, we are going to turn our focus to tasks and put our systems analysis skills to use by tbreaking down the actual tasks that users go through in the context of our larger set of project tasks.

More notes...

• Wei, J., & Salvendy, G. (2004). The cognitive task analysis methods for job and task design: review and reappraisal. Behaviour & Information Technology, 23(4), 273–299. http://doi.org/10.1080/01449290410001673036
  • Skim this for reference purposes. Some of the concepts might be useful to you.
• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Five Hat Racks," p. 100,
  • "Flexibility-Usability Tradeoff," p. 102,
  • "Iconic Representation," p. 132,
  • "Mapping," p. 152.

Presently, the interface offered by GNURadio Companion effectively gives a user a path to all of the information available about the varibles and settings related to their task, provided they already know the path. This is sub-optimal for novice users, and for some experienced users. Today we will work on breaking down those tasks into information maps to lead users operating at different levels through and applying them in our various areas of specialization.

More notes...

• Toms, E. G. (2002). Information interaction: Providing a framework for information architecture. Journal of the American Society for Information Science. American Society for Information Science, 53(10), 855–862. http://doi.org/10.1002/asi.10094
  • Skim this, but pay special attention to the last two pages.
• Adams, J. L. (2001). Conceptual blockbusting: A guide to better ideas. Cambridge, Massachusetts: Perseus Publishing.
  • Read the following chapters in Conceptual Blockbusting:
  • 2 ("Perceptual Blocks," pp. 15-36) and
  • 3 ("Emotional Blocks," 37-56).

More notes...

• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Consistency," p. 57,
  • "Constancy," p. 58,
  • "Control," p. 64.

More notes...

• Klein, H. A., Lippa, K., & Lin, M.-H. (2010). As Human-Computer Interactions Go Global. In C. C. Hayes & C. A. Miller (Eds.), Human-computer etiquette: Cultural expectations and the design implications the place on computers and technology (pp. 15–33). Boca Raton, Florida: Auerbach Books. Link
• Cyr, D., & Trevor-Smith, H. (2004). Localization of Web design: An empirical comparison of German, Japanese, and United States Web site characteristics. Journal of the American Society for Information Science. American Society for Information Science, 55(13), 1199–1208. http://doi.org/10.1002/asi.20075
• Adams, J. L. (2001). Conceptual blockbusting: A guide to better ideas. Cambridge, Massachusetts: Perseus Publishing.
  • Read the following chapters in Conceptual Blockbusting:
  • 4 ("Cultural and Environmental Blocks," pp. 57-76) and
  • 5 ("Intellectual and Expressive Blocks," 77-96).

More notes...

• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Immersion," p. 134,
  • "Performance Load," p. 178,
  • "Rosetta Stone," p. 206.

More notes...

• Miller, L. (2015). The Practitioner’s Guide To User Experience Design. New York: Grand Central Publishing.
  • Read chapter 3, "Interface Designs are the Facial Expressions of Digital Products," pp. 70-84.
• Adams, J. L. (2001). Conceptual blockbusting: A guide to better ideas. Cambridge, Massachusetts: Perseus Publishing.
  • Read the following chapter in Conceptual Blockbusting:
  • 6 ("Alternate Thinking Languages," pp. 98-126).
• Tufte, E. R. (1997). Visual Explanations Images and Quantities, Evidence and Narrative. Cheshire, Connecticut: Graphics Press.
  • Read chapter 4, " The Smallest Effective Difference," pp. 72-77.

More notes...

Today we will meet in groups and I would like you to fill out the evaluation form linked below.

Mid-term self-evaluation

More notes...

More notes...

More notes...

Today we will discuss tool choice and what it means when we use one tool over another. We'll also talk about how tools are not an accident of circumstance. They all have specific design constraints that came along with their development and the worldview of their authors embedded within.

We will watch this TED talk by Clay Shirky on open source government.

More notes...

More notes...

• Norman, D. A. (2013). The Design of Everyday Things: Revised and Expanded Edition. New York: Basic Books.
  • Read chapter 4, "Knowing What to Do: Constraints, Discoverability, and Feedback," pp. 123-161, and
  • chapter 6, "Design Thinking," pp. 217-257.

More notes...

For today I would like you to think about one feature for our GNURadio-based project and describe it in an issue on GitHub in the repository where you are primarily working. Be responsive to the following:

1. What does this feature afford users?
2. What are its constraints and how do they help or hinder users?
3. How does the feature signify its affordance or how to use it to users?
4. What conventions does this feature either respond to, incorporate, or reject, either in the context of interface design generally or GNURadio specifically?
5. How will you go about arguing for the inclusion of this feature?

Get creative with this, but make it a very, very specific feature, rather than a general one. You can upload pictures, code snippets, or anything else you want along with the issue.

More notes...

• Norman, D. A. (2013). The Design of Everyday Things: Revised and Expanded Edition. New York: Basic Books.
  • Read chapter 3, "Knowledge in the Head and in the World," pp. 74-122, and
  • chapter 5, "Human Error? No, Bad Design," pp. 162-216.

Thryn, "Design thinking lessons from our cats," https://hackernoon.com/design-thinking-lessons-from-our-cats-9a43fd71457a

Important comic about documentation: http://www.commitstrip.com/en/2017/02/20/no-ones-fault/

Today in class we are going to look at one of the worst modes of documentation and user education and speculate about ways to fix it:

Terms of Service; Didn't Read, https://tosdr.org/

In pairs, you will select a ToS and do some basic sleuthing about it.

I want to know:

• Name of site/service
• Main URL of site
• URL of ToS
• How many clicks from homepage?
• Mechanism for affirming reading and agreement
• Word count of ToS (https://wordcounter.net/website-word-count)
• Reading level of ToS (https://www.webpagefx.com/tools/read-able/)

We'll put all this in a spreadsheet online: https://goo.gl/7BIf7H

More notes...

Today we're going to sketch up the features that we looked at last week and write a piece of documentation for them.

In the documentation, I want to see you describe:

1. What the feature does (functionally) for a user.
2. Expected user inputs (what does the user do?) and program outputs (what can the user expect in response?).
3. Possible errors that may result (if any) and corrective suggestions for user.

Put this all in comments on the issue that you created last week. Alternatively, you can do the work elsewhere and link to the files in the comments.

More notes...

• Nielsen, J. (2003). Paper Prototyping: Getting User Data Before You Code. Nielsen Norman Group. \urlhttps://www.nngroup.com/articles/paper-prototyping/. Retrieved from https://www.nngroup.com/articles/paper-prototyping/
• Farrell, S. (2015). Test Paper Prototypes to Save Time and Money: The Mozilla Case Study. Nielsen Norman Group. \urlhttps://www.nngroup.com/articles/mozilla-paper-prototype/. Retrieved from https://www.nngroup.com/articles/mozilla-paper-prototype/

We will watch several of the videos in this 3-part series on prototyping from Google.

The first deals with paper prototyping:

The second looks at translating into screen prototypes:

More notes...

• Lidwell, W., Holden, K., & Butler, J. (2010). Universal Principles of Design (2nd ed.). Beverly, Massachussetts: Rockport. Retrieved from http://site.ebrary.com.libproxy.lib.unc.edu/lib/uncch/detail.action?docID=10715587
  • Read "Archetypes," p. 28 and
  • "Prototyping," p. 74.

Today we're going to translate our paper prototype into a screen-based prototype using the online tool: http://concept.ly

Sign up for an account before class at https://app.concept.ly/home/signup.vz

More notes...

• Wimberly, C. (2015). 5 prototyping tips that will improve your process. InVision Blog. \urlhttp://blog.invisionapp.com/5-prototyping-tips-that-will-improve-your-process/. Retrieved from http://blog.invisionapp.com/5-prototyping-tips-that-will-improve-your-process/
• Odysseos, A. (2016). 10 Indispensible App Prototyping Tips from Successful Designers. Proto.io Blog. \urlhttp://blog.proto.io/10-indispensible-app-prototyping-tips-from-successful-designers/. Retrieved from http://blog.proto.io/10-indispensible-app-prototyping-tips-from-successful-designers/

The third video in the Google series on prototyping deals with native prototyping, or building prototypes using actual code and devices.

We'll watch it together in class, but it is a good idea to have a look at it beforehand as well.

More notes...

More notes...

• Muldoon, N. (2011). Usability Testing with Paper Prototyping. Atlassian Blogs. \urlhttps://www.atlassian.com/blog/archives/usability-testing-with-paper-prototyping. Retrieved from https://www.atlassian.com/blog/archives/usability-testing-with-paper-prototyping
• Naji, C. (2016). Usability Testing With Prototypes. Usability Geek. \urlhttp://usabilitygeek.com/usability-testing-prototypes/. Retrieved from http://usabilitygeek.com/usability-testing-prototypes/
• Cao, J. (2016). Paper Prototyping: The 10-Minute Practical Guide. Studio by UXPin. \urlhttps://www.uxpin.com/studio/blog/paper-prototyping-the-practical-beginners-guide/. Retrieved from https://www.uxpin.com/studio/blog/paper-prototyping-the-practical-beginners-guide/

Watch this walkthrough of a paper prototype user test. Pay attention to what is happening at each stage and in each scenario. How might this technique be used in our project?

More notes...

https://www.buzzfeed.com/andyneuenschwander/18-people-who-really-shouldve-gone-to-design-school?bffbmain=undefined&ref=bffbmain&utm_term=.tmQm0yeMX#.ki4QvAo9j

More notes...

More notes...