Reading responses are scored out of 2 points; getting a 2 means you received full credit. Reading responses are part of your Class Participation grade.
0 means you submitted late or didn't submit at all.
1 means you didn't completely answer the prompt.
2 means your response contributed much more to the discussion that just recapping/summarizing the readings.
Describe a recent frustrating experience you have had interacting with a digital device or system. Discuss how following the design process outlined in the reading could have improved the design.
I have always been an avid user of Snapchat but one thing that frustrates me is its user interface. Last week, I snapped a picture and sent it to the 15 members of my club. However it took an extremely long time to go through my entire friends list of 150+ people to select those 15 people because the friends list is sorted alphabetically. Today I wanted to do the same thing and was extremely frustrated that I had to repeat the entire process again.
In order to improve on this system we have to first figure out who is going to use this app. Most people using this app are teenagers and young adults. Most teenagers aren't going to have just a couple dozen of friends added; they're going to have hundreds. Recognizing this issue would make it necessary for an easy way to organize people on their list of friends. A representative task for this app would be for someone in this target demographic to snap a photo and send that photo to fifteen friends who are in the same club.
Next it would be best to plagiarize the way that Facebook sorts its messenger. Currently, Snapchat has three ways to sort your friends: best friends, most recent, and alphabetically. If you have 15 people to send your snap to, and only one person is on your best friend's list and one person is on your most recent list, then any of these methods are useless. The way Facebook allows you is through the following three ways: suggested friends, your own groups, and alphabetical. This method is much more intuitive, because if you wanted to send a picture to people from the same club, you could just make a group on Snapchat for that club, then snap the photo, select that group, and send it. Then the next time you want to send to the same group, you would not have to select each person individually again. Next using GOMS analysis and figuring out how many steps it would take for someone to add a group and send multiple photos to that group will verify the need for groups in the app.
I believe that adding a group function to the Snapchat friend list will surely make the lives of its users less frustrating and hopefully they do so in the future.
When entering a recurring event into Google Calendars, you’re able to choose how often you want an event to happen, daily, weekly, every weekday, whatever you want. These options are listed as a 7 checkboxes, one for each day. However, if you select all days M-F and try to update the days the event is supposed to recur, the checkboxes disappear and they show up as “Daily” instead. The only way to reassign the days is by deleting the event and creating a new event. Whoever designed the interface must have reasoned that switching to “Daily” makes it more convenient to easily view which days have been selected, which is true. However, it prevents the user from updating their preferences.
(This response would receive a 1 because it does not relate the user’s frustration to the design process referenced in the reading.)