Tag: final project

Abstract

Many platforms that enable connection and bonding despite physical location already exist; separately, many music streaming services are already in operation. However, few platforms bridge the gap between music and social connection, despite the many opportunities for bonding and sociability that music can create. In order to bridge this gap between music and social connection via distance, we propose an extension to Spotify which allows multiple users to stream the same playlist of songs simultaneously. The primary purpose of this extension is to create a new avenue for social connection and deepening community through music, especially for groups dispersed across large distances or who are otherwise unable to be physically together. In this paper, we survey relevant findings from existing literature on the Spotify platform, identify a need for sociability and agency, formulate four use-case types to our proposed extension, then conclude by discussing its limitations, implications of its use, and future directions for its design as an intervention into music and social spaces of a connected world.  

Concept Overview

House Party is an extension that runs on top of the Spotify platform that may be used on either a computer or a smartphone. This extension allows multiple users in different locations to stream the same playlist of songs simultaneously. This extension does not alter the core functionality of Spotify, but rather builds onto Spotify’s existing features to improve the app and give users a new experience within a familiar platform. The primary purpose of this extension is to create a new avenue for social connection and deepening community through music, especially for groups dispersed across large distances or who are unable to be physically together for any reason. 

Design Audience 

The intended audience for House Party can be summarized as follows: They are Spotify users from age 15-30 who value music, emotional and social connection with others, and agency and diversity in their musical selections.

Although any Spotify user could certainly successfully download and use the extension, House Party will specifically be designed with younger Millennial and Gen-Z users of the platform (around age 15 to age 30) in mind, as they are more likely to have the habits, interests, and technological savvy that would make this product desirable. Furthermore, the Spotify user base already skews toward this younger demographic, as a 2018 Goodwater Capital survey found that Spotify is the most used music streaming service for people under the age of 30.¹ House Party will not target users based on gender or location, though it should be noted that the existing Spotify user base is overwhelmingly American and European (over 65% combined), with Latin America comprising a significant minority (22%) and users from the rest of the world totaling 13% of the user base.²

These Millennial and Gen-Z users are used to being in constant connection with friends, family, and other groups with which they identify. From social media such as Instagram and Twitter to text messages to large-scale social events such as concerts and sporting events, our target audience enjoys both physical and digital interaction with others. This is especially true of interactions with friends, significant others, and other close relationships – Event Manager Blog reports that millennials are more likely to attend an event if they can do so with friends,³ and these findings appear to map onto digital activities as well. Though many forms of digital interaction already exist with great success, few music-centric platforms have social functionality, despite scientific evidence that listening to music together can play a role in closeness and connection.⁴ This is especially troubling in the age of a global pandemic, where large-scale musical gatherings like concerts and festivals are postponed until further notice, and even small-scale gatherings of friends are prohibited (or at the very least unwise). 

Beyond its connecting capabilities, Millennials and Gen-Z users value music on its own: A 2018 survey by digital media company Sweety High found that 94% of Gen Z respondents cited music as “important” or “very important” to their lives,⁵ and a 2017 report by Spotify states that 3 out of 4 Millennials say music is part of how they define who they are.⁶ Both generations tend to have musical tastes that span across genres, with songs from multiple genres often played in succession within the same listening session.⁷ Therefore, while “old-school” options such as radio, or recent developments in live-streamed concerts and festivals, allow for connection via music despite distance, these avenues often lack the musical diversity our target audience desires. Furthermore, users have no agency in the artists or songs that are played, despite the fact that ⅓ of user time on Spotify is spent listening to user-generated playlists, suggesting a desire to be in control of or influence the musical selection a significant portion of the time.⁸ Data from our own pilot survey of  music streaming platform users, all of whom fall into Gen Z and Millennial age groups, correlated with these findings, as most respondents indicated a strong interest in having agency in the types of music they listen to, as well as in their experience of the platform in general.⁹

Background Analysis

Many platforms that enable connection and bonding despite physical location already exist; separately, many music streaming services are already in operation. However, few platforms bridge the gap between music and social connection, despite the many opportunities for bonding and sociability that music can create.

While social media platforms have become nearly inumerable, a few stand out as major players. According to Search Engine Journal, the seven most popular social media platforms in 2020 are (in order) Facebook, Twitter, LinkedIn, Instagram, Snapchat, Pinterest, and Reddit.¹⁰ All of these platforms allow for varying degrees of social connection across distance, often through direct messaging users, posting updates through statuses or stories, or commenting on posts. Some platforms even engage music directly – some notable examples include Instagram’s ability to add clips of songs to Stories, as well as Facebook groups and subreddits dedicated solely to discussions of a particular band. However, these capabilities remain somewhat limited: Instagram Stories only allow up to 15 seconds of a song to play at a time, and threads discussing more popular bands can often be large and unruly, involving hundreds or even thousands of users and therefore missing the intimacy of a conversation between friends or a few die-hard music lovers.

Many music streaming services exist as well: Goodwater Capital classifies the major music streaming platforms as Spotify, Pandora, Apple Music, Google Play Music, Amazon Music, and Soundcloud.¹¹ Of these, Spotify, Apple Music, Google Play Music, and Amazon Music function quite similarly: They all allow users to search and stream music, create their own playlists, and browse pre-generated playlists often based on algorithms. Pandora, meanwhile, does not center itself around playlists but rather generates a continuous stream of music based on a user’s initial input of one or multiple artists or songs. (It should be noted that Pandora does allow some playlist functionality, but this is only available with a Premium membership, which costs $9.99 per month; neither the Free nor the $5.99 Pandora Plus memberships allow users to create their own playlists.¹²) While Soundcloud does allow the creation of playlists for all users, the platform focuses primarily on the relationship between artists and their fans, allowing users to comment directly within tracks¹³; it is also primarily used by artists who are not signed to any particular record label and therefore tend to have smaller followings. While this ability to form connections between artists and fans is important, it leaves little room for fans to connect with one another.

Therefore, from our survey of existing social and musical platforms, two important conclusions can be drawn: Social platforms offer limited ability to engage with music directly, and music platforms offer little opportunity to connect with fellow music lovers.

Intervention Rationale

In order to bridge this gap between music and social connection via distance, we propose an extension to Spotify which allows multiple users to stream the same playlist of songs simultaneously. The purpose of the extension is to allow for emotional connection and deepening of community through music, a function which both major social networks and major music streaming services are currently lacking.

     Part One: Why Spotify?

A 2018 report by Goodwater Capital found that Spotify ranked highest in user satisfaction across multiple measures, among the major music streaming services Pandora, Spotify, Amazon Music, Apple Music, Google Play Music, and Soundcloud.¹⁴ Of these platforms, the report also found that Spotify has the highest percentage of users under 30 and ranked as a favorite among younger users.¹⁵ These stats are important for multiple reasons. First, because House Party functions as an extension of, rather than an amendment to, Spotify’s core functionality, it is important that users are already generally satisfied with their experience. Many survey respondents noted that they intended to maintain or increase their usage of the platform, and a common sentiment was that of using the service every day.¹⁶ These findings bode well for an extension that introduces additional functionality to an already well-loved service. Next, House Party’s target audience is younger Millennial and Gen-Z users aged 15-30. Since Spotify’s existing audience already skews toward and is a favorite of this age group, it is likely that they would be interested in an extension that builds atop a platform they already know and use.

Pilot Survey & Initial Findings

In order to further understand current uses and limitations to Spotify, we designed a pilot survey for an initial sampling of members from our MAS.S67 Fixing Social Media, at first with a small group of peers during our class, and later with the general mailing list after our class. The pilot survey consisted of three central questions: “how do you use Spotify currently?”, “what are some of your surprising/unexpected uses of Spotify?”, “what can’t you do with Spotify?”. We built the pilot survey to collect responses using Google Doc (in-class) and Google Forms (after-class), after which we imported each set of responses into a table. We then used MIRO, an online whiteboard for collaborative work, to code responses for themes using an approach to qualitative analysis resembling an open card sort, in which responses are cards to be sorted by categories to be determined through the sorting, rather than before the sorting. This approach not only allowed us not only to sort cards (responses) by categories (themes) as they emerged, but also map both first-order and second-order connections between cards across the different categories. Additionally, each response in a given set of responses was assigned one of three colors based on which of the three pilot survey questions it submitted as a response to. All of the responses were coded using the same categories, which included whether a given response mentions agency, mentions algorithms, mentions content, mentions platforms, mentions sociability, mentions device use, or mentions purpose. Cards mentioning several of these themes underwent an additional step, in which each of the categories interpreted were ranked by importance. These rankings determined placement of the card on a first category (most important), a first-order connection to another second category (second most important), as well as a second-order connection to another a third category (third most important), where the first-order connection is a line matching the color of the given card (blue, green, red) and the second-order connection is a line matching the color of all the categories (yellow). From this exercise, we found that agency, sociability, and purpose appeared most often in responses, and that most responses were traceable to sociability as either a first-order or second-order theme.

• 

• 

     Part Two: House Party’s Purpose

House Party’s purpose is to enable new forms of emotional connection and deepening of community through music, especially when that connection is not able to occur in the same physical space. This idea sprouted from an experience co-author Elon had while quarantined during the COVID-19 pandemic. Each week, she and a group of friends met over video chat to talk and play games. She was listening to music over her Bluetooth speaker, and her friends could vaguely hear the music through the video chat. Eventually, a song came on that everyone liked, and they all spontaneously began to dance – a dance party that spanned from Nashville, TN to Pensacola, FL to Incheon, South Korea, nearly 7000 miles total. After the song ended, the mood of the group had palpably lifted. This experience helped Elon realize how important music can be in creating bonds, and that it can be a useful tool in connecting people regardless of their location or ability to be together. This revelation inspired her, and she wondered how she might create something that allows groups to connect and bond over music – together, at the same time – even from thousands of miles apart. Thus, the idea for House Party was born, and with it its purpose to bring people together through music – from anywhere and for any reason.

The extension’s name, House Party, has a double meaning. First, it’s a tongue-in-cheek reference to the fact that people all over the world are confined to their homes during a pandemic, such as COVID-19; therefore, any party is quite literally a house party. Beyond this, though, House Party is meant to evoke the feeling of a more traditional house party – a highly social event that brings people together, in which the mood is kept up by music, and where any attendee can hear the same music as everyone else, regardless of their location in the house. Of course, it is worth noting that Houseparty, a video conferencing app, already has a markedly similar name; however, we believe that our extension is truer to the spirit of a house party, and that since it is a music-centric extension rather than a video-centric standalone app, it is sufficiently distinguishable from the Houseparty app.

Platform Infrastructure & Relevant Features

As a digital platform, Spotify relies on a technical infrastructure to sustain its functionality as a both an user application and as a media services provider. In particular, Spotify’s technical infrastructure is built with a microservice architecture, allowing each layer of its platform stack to remain at once maintainable and testable by both software engineers and product developers. In 2011, Spotify introduced Spotify App Finder, a service for third-party developers to create and host apps for use by members who had Spotify Premium. In 2014, Spotify discontinued this space for third-party developers upon introducing a Web Application Programming Interface (API), which it claimed would fulfill many of the advantages to App Finder. In this time, spaces for synchronous playback experiences had emerged on the Spotify platform, through the group listening rooms of Soundrop, a third-party app around which a community formed. However, because the App Finder API had been discontinued, Soundrop was forced to close. As a result of this closure, efforts to build open-source alternatives, such as Soundbounce, were soon formed yet inevitably relegated to remaining standalone players, in which Spotify Premium members have to log-in through a separate app, until Spotify enables developer support for apps in their Web player. In the six years since then, Spotify has yet to have made this decision.

As a digital platform, Spotify currently offers three features that are relevant to our proposed intervention. First, Spotify publicly allows synchronous “group sessions”, in which users can add songs to a shared song queue with a limitation of one device playback at any time. Second, Spotify publicly allows asynchronous “collaborative playlists”, in which users can add songs to a shared song list which multiple devices can playback at any time. Third, Spotify privately allows synchronous “social sessions”, in which users can add songs to a shared session, multiple devices can playback, and invite other users to listen along together at once, wherever they are. Despite this feature being most relevant to our extension, it’s only usable for Spotify employees.

User Journey & Use Cases

House Party is designed with two primary use-case-types in mind. However, we envision two additional use-case-types that could be implemented with additional functionality, perhaps in a subsequent update to the extension. The primary use-case-types can be characterized broadly as one-to-one and many-to-one, and the envisioned future types can be characterized as one-to-many and many-to-many.

Primary Use Case 1: One-To-One

In a one-to-one case type, a group of users are given access to a collaborative Spotify playlist. Users with editing access may add and remove songs in the playlist (as is currently the case with Spotify’s ‘collaborative playlists’ feature), but these users also all have the ability to turn House Party Mode on or off. When House Party Mode is on and a user hits play on the playlist, all users with access will receive a push notification to “Join the Party.” Any user who then tunes in will then hear the playlist simultaneously with other users. Anyone with access may queue up or skip songs, or play or pause the music. This will remain the case until House Party Mode is turned off.

A first imagined use case within this type is that of a party among friends, thrown over a video chat app such as Zoom or Facetime due either to distance or inability to congregate. Before the party, one friend would create a collaborative playlist and invite all their friends to contribute songs. During the party, each friend could hear the same music from their respective speakers as they chat, and any friend could skip a song, pause the music, or queue up a song they’d like to hear. A second imagined use case within this type is that of a couple in a long distance relationship who would like to feel connected to one another as they go about their daily routines. Each partner would contribute to a collaborative playlist with songs they both enjoy or that they would like to introduce to the other, and they would listen together as each partner gets ready for work in the morning.

Primary Use Case 2: Many-To-One

In a many-to-one case type, multiple users can access, edit, and control the playlist in the same way as a one-to-one case type. However, in this case, another user can stream the playlist without having these same privileges. Those with control privileges would access the playlist through the collaborative playlist function, and any of them may turn House Party Mode on, queue up or skip music, etc. The user without control privileges would access the playlist by a link, subscription, or search (if it is publicly searchable within Spotify). When House Party Mode is turned on, all those who are collaborators (with control privileges) and the listener (if subscribed to the playlist) would receive a “Join the Party” notification. 

An imagined use case within this type is a group of friends gifting a Spotify playlist to another friend for their birthday. All those gifting the playlist would contribute to the collaborative playlist, and once it was complete the group would send a link to the playlist to their friend. The group would agree on a time to listen together, and the friend whose birthday it is would be delighted at all the songs their friends have chosen to play.

Future Use Case 1: One-To-Many

In a one-to-many case type, only one user has access to the playlist and therefore is the only one with the ability to add and remove songs, turn House Party Mode on and off, and queue up, skip, play, or pause the playlist. Other users may reach the playlist through a link or subscribe to the playlist (if it is publicly searchable within Spotify), but they cannot make any changes; however, those who are subscribed will receive a “Join the Party” push notification when House Party Mode is turned on. The “host” user can publicize the time they planned to stream the playlist so that other users knew the time to tune in.

Imagined use cases in this category are well-known local or national DJs compiling a list of songs for a Friday night quarantine dance party and artists hosting live listening parties for their new (or old and well-loved) albums.

Future Use-Case 2: Many-to-Many

Finally, a many-to-many case type would operate in mostly the same way as a many-to-one case type, except that multiple listeners may synchronously stream the playlist instead of one. As in the previous case, any user with control privileges can turn House Party Mode on and off, queue up or skip music, etc. Users without control privileges may access the playlist by a link, subscription, or search (if it is publicly searchable within Spotify). Furthermore, any of the host users may publicize the time they planned to stream the playlist so others knew when to tune in.

Imagined use cases in this category are groups of friends creating a playlist to stream to their wider friend circles and multiple artists co-creating and streaming a playlist for their fans.

Of course, House Party’s capabilities should not be limited to these particular use cases. Certainly, the extension’s target audience is known for their creativity and ingenuity, and there is no limit to the situations in which they can apply it. These use cases are simply a jumping-off point, with the four broad types serving to showcase the extension’s functionality in different situations.

• 

• 

Intended Experience

As previously stated, the purpose behind this intervention is to create a new avenue for connection and community through music, especially in times when groups are unable to be together physically. The technical goal of the project is to successfully function atop Spotify’s existing user interface while providing users a new option in their experience of the platform. Success in reaching both of these goals may be measured in how well House Party meets several objectives. Objectives measuring success include the following:

• Number of users who install the extension
• Number of users who use the extension on a daily, weekly, or monthly basis
• Variety of use cases in which the extension is implemented (determined by surveys)
• Overall user satisfaction with the extension (determined by surveys)
• Sense of deepened community and social bonding between users (determined by surveys)
• Regularity of bugs or crashes which make the extension difficult or impossible to use 
• Legal or technical issues that arise with Spotify that make the platform inhospitable to the extension

Limitations, Implications, & Future Directions

Certainly, the House Party extension has a number of limitations, implications, and avenues for improvement. A major limitation of the extension in its current state is that it works best with Spotify Premium (which costs $9.99 per month)¹⁷ and would not work as well with Spotify Free. This is because Spotify Free users only have access to a limited number of song skips per hour and must listen to an ad after a certain number of consecutive songs.¹⁸ If users with Spotify Premium listened synchronously with a Spotify Free user, it is likely that the entire group would have to listen to the ads alongside them, and the Free user would be unable to access the full functionality of the House Party extension without the ability to skip songs. Another limitation is that House Party can’t access songs outside of Spotify’s existing library. This means that as far as the extension could enable sociability, the diversity of music itself would be determined by the catalogue of artists and albums made available through Spotify.

House Party brings foreseeable implications as well. First, the extension may further entrench people in the music preferences of their existing networks or the social groups with which they identify. We believe this concern could be resolved in part by using in-app prompts from Spotify that suggest music from music or artists outside the collective preferences at play when House Party mode is turned on. Second, this extension could become another way for trolls to access or to otherwise cause harm to communities. We believe this concern could be resolved in part  through increased security around playlist link sharing such that when using House Party is in use and a playlist is shared with different listeners or users, they are brought into a waiting room before being allowed access to editing capabilities of the playlist. We believe implications like these have become part and parcel of designing social media, in a world where various online platforms have come to face nearly identical concerns in recent years.

Finally, a number of future improvements could be made to this extension. First is additional functionality that would allow our envisioned future use-case-types to be viable, as the extension is currently designed to work best on a small scale, likely with groups who know one another personally. Future improvements could allow the extension to scale up and work for mass audiences so that artists, DJs, or others with large followings could stream to all their fans at once. This could also include the addition of a comments feature, perhaps similar in form to Facebook Live, where listeners could make requests, reach out to the host(s) with comments, or discuss the music with other listeners. A second future improvement is that of an algorithm that enables the extension to do more of the work of ordering and fitting songs together in a playlist so the music flows together smoothly: Although the users would retain total agency of the songs within a playlist, the extension would reorder the songs for a more seamless listening experience. Of course, some users may feel uncomfortable with the use of an algorithm in any form, so this feature would remain entirely optional.

References

1. Understanding Spotify: Making Music Through Innovation, Goodwater Capital, March 15, 2018, https://www.goodwatercap.com/thesis/understanding-spotify#important-disclosures. 
2. Mansoor Iqbal, “Spotify Usage and Revenue Statistics (2020),” Business of Apps, April 24, 2020, https://www.businessofapps.com/data/spotify-statistics/.
3. Kelli White, “How to Attract and Engage Millennial Attendees for Your Event,” Event Manager Blog, October 17, 2018, https://www.eventmanagerblog.com/how-to-attract-millenials-for-event.
4. Jill Suttie, “How Music Bonds Us Together,” Greater Good Magazine, June 28, 2016, https://greatergood.berkeley.edu/article/item/how_music_bonds_us_together.
5. Brittany Hodak, “New Study Spotlights Gen Z’s Unique Music Consumption Habits,” Forbes, March 6, 2018, https://www.forbes.com/sites/brittanyhodak/2018/03/06/new-study-spotlights-gen-zs-unique-music-consumption-habits/#22b9970d42d0.
6. Spotify for Brands, “Culture Next,” Global Trends Report, no. 1 (2019): 1-19. https://www.spotifyforbrands.com/en-US/insights/millennial-guide/
7. Spotify for Brands, “Culture Next,” and Brittany Hodak, “New Study Spotlights Gen Z’s Unique Music Consumption Habits.”
8.  Mansoor Iqbal, “Spotify Usage and Revenue Statistics (2020).” 
9. Data collected in pilot survey conducted April 29, 2020.
10. Kristi Kellogg, “The 7 Biggest Social Media Sites in 2020,” Search Engine Journal, February 3, 2020, https://www.searchenginejournal.com/social-media/biggest-social-media-sites/#close.
11.  Understanding Spotify: Making Music Through Innovation. 
12.  “Music and Podcasts, Free and On-Demand,” Pandora, accessed May 2, 2020, https://www.pandora.com.
13. “Creators on SoundCloud,” SoundCloud, accessed May 2, 2020, https://creators.soundcloud.com.
14.  Understanding Spotify: Making Music Through Innovation.
15. ibid.
16. ibid.
17.  “Spotify,” Spotify, accessed May 2, 2020, https://www.spotify.com/us/premium/.
18. Henry T. Casey, “Spotify Free vs Premium: Should You Pay to Play?,” Tom’s Guide, March 28, 2019, https://www.tomsguide.com/us/spotify-free-vs-premium,news-24850.html.

Summary

So much discussion is happening these days that is backed up with data visualization (charts or graphs), but the problem is, misinformation and trust issues could arise due to the fact that these visualizations are not fully understood, or can’t be reproduced to more accurate versions unless the author of the chart decides to do so.  In this work, I explored simple and lightweight workflows to democratize the process of discussing data on the web for social and knowledge seeking purposes. I looked into existing tools that empower users to visualize data on the web but they are disconnected from where the discussion is happening (i.e. social media). I have built “vizdat!” a solution that is a layer over online communities that discusses data visualizations (charts) to allow community members to visualize and reproduce charts in-situ to improve the commenting experience and enrich online discussion around charts.

Background and Motivation

Whenever there is data shared on the web as a chart and there is a comments section, the discussion is often only in text [e.g The Upshot, The Economist, Reddit, etc.]  Imagine you are on twitter, a blog or reddit. You saw a chart (visualization) but felt something was wrong or wanted to discuss or add something to that chart. The way the web currently works, is that a person shares a chart online and in the comments people are only allowed to reply with text!

I asked one of r/dataisbeautiful moderators about how to share charts in comments, and his answer was the following

There has to be a better way to discuss charts online! What if we make the comments section more visual and interactive . What if we enable users to comment with charts, not just text, to extend the discussion around the data story even further. That’s where vizdat! comes in. vizdat! is a website + a chrome extension that changes the UX of online communities to enable users to discuss interactive charts with interactive charts, instead of just text.

Design Research

The idea started when I started talking to social media influencers who like to share media in general with their audience. I started exploring the question:  How might we enhance the commenting experience online?

This question felt too broad so I narrowed down the commenting experience on media that is in the form of charts and graphs. So I focused instead on: How might we facilitate online discussion around charts? In order to narrow down the design scope even further I looked into quantified self communities, data journalism outlets, twitter, facebook and reddit. Discussion around charts is everywhere yet, text comments are the norm! so: How might we make visual comments anywhere, anytime on the web? That is my main research question. 

For this design document, I narrowed the audience down to one interesting and safe community, which is r/dataisbeautiful on reddit. I have improved my prototype around the technical and social constraints in that community. How might we improve discussion around data on r/dataisbeautiful? In order to answer that question for this project I have performed the following: 

→ digital ethnography

→ contextual analysis

→ need finding

→ built vizdat based on the identified needs

→ posted on reddit, but not so much traffic to my stories, and some of them got removed. (stricts moderation)

→ reached out to mods, I wasn’t allowed a recruitment message

→ created a subreddit that simulates r/dataisbeautiful with all it’s restrictions and rules (e.g. no posts with text only links and images, original post must be marked with OC and so on).

→ usability tested and observed how users react on that simulated community 

Interview

I interviewed a Quantified Self speaker who is also a social media influencer. I was curious about how he shares his data with his huge audience. For example, he is a runner and he uses Strava to share his runs as shown in the image below. He does have a huge following on the app but he only gets likes as opposed to comments. 

He tried sharing the same charts on facebook and reddit and he rarely got any meta comments or any useful comments. When he spoke at QS he shared his data with like minded people and according to his words he loved the comments and insights he got from people who were interested in his data. In my interview with him he made the following comment:

I would love it if I could have people like me look at my data and I look at their data whether it’s a log data from running experience or so and then comment on them a meaningful comment that would be nice but the current apps don’t allow this the only thing that I get from sharing my log is people asking me about the best running shoes or how do you get yourself to run and stuff like that which is not relevant to the data I’m sharing and that’s two to the app limits in my opinion

I followed up with him by asking him what he meant by a meaningful comment and his reply was:

Meaningful comments to me would be something that is:

• investigating the WHY or pointing to insights from the data or story.
• asking a question/comment that would make me think or curious to figure out. (such as this follow-up Q) 
• A comment suggesting different/new efficient methodologies.

The points in bold are features I have considered when building my solution “vzdat!”.

Need Finding

In addition to talking to prospect users, I looked into different communities where data is discussed. I first looked at news outlets such as The Upshot and The Economist and social media websites such as twitter. My goal was  to identify recurring patterns and practices around discussing charts as shown in the snapshot below.

It was clear that there were general patterns. When data is discussed over the web in a lightweight format (e.g tweets, comments, blogs replies etc) users tend to use a lot of numbers. The following are the main tasks ordered:

• The discussion involved replies and comments on the visualization wanting to know how to reproduce (asking for data and code)
• Replies had users pointing at numbers in the visualization or actually screenshotting and replying with the image with their comments.
• Design Critique on the type of visualization used or other aspects of design like color and text.
• Comments involved teachers and members of the community expressed their intent to use those visualizations to educate their community about the domain in which the story of vis is about. (purpose of narration) guided tour (videos to show) gapminder Keyframes in creating animated interactive visualization (narrated visualization) (northwestern) (

Domain experts who started a vis story, reply to people’s questions about the domain with more visualizations.

Scope

For the sake of this milestone and class, I narrowed down the scope of my audience to a safe community on reddit called r/dataisbeautiful. According to their definition of the community: it’s “a place to share and discuss visual representation of data: Graphis, charts, maps, etc.”  The community lists many posts that are a composition of a visualization with a title and a description by the author of how it was made and his or her design rationale. In addition to that, users can comment on the main story and reply to each other. The community is for professionals and amateurs, experts and novices. I looked where the action is and it’s in the community itself in addition to “discord” (the chat community associated with it). The posting rules of this community are simple. Anyone can post as long as their post contains a data visualization, mention the source data and indicate if it’s their original contribution or not.

Qualitative Work

In order to better understand and identify the  needs of r/dataisbeautiful I followed a mixed approach. I participated as a member and as an observer in r/dataisbeautiful. I used content analysis [6] and participation observation [3]. I wanted to ground my work so I looked into 7 reddit posts with more than 500 comments, I coded the comments with open codes and iterated 2 times until I felt I have a saturated list. The first pass helped me identify general trends in the community. The second pass was to saturate and confirm my coding. 

Digital Ethnography and Contextual Inquiry 

I spent almost 4 months in r/dataisbeautiful as an active member. I looked into how users comment on each other and on the main post. What I find very fruitful about that community is the nature of comments.

Most comments are meta talking about the visualization or chart. As we will see in the codes section, a lot of these comments were critiques, either the data, chart type, analysis or aesthetics. There was also a tendency to reproduce work and share it either as a new post or in the comments. Some users talk about aspects of the visualization configuration.Others address data issues that were clearly manifested by the data visualization. (users see triggering component  in the vis, look at the dataset as a result then comment) 

While coding the data I looked into intentions of users, why: critique, suggest, inquire etc. I also looked at how and what users comment, while reddit is strict regarding the comments and only allows text. Some users post links either to their improved visualization or their suggestions to the main author. Finally I also looked at who the audience is, the author and the commenters. I identified some personas in which I can design for which includes learners and experts. The following snippets are screenshots of comments on different posts. From these comments I was inspired with the functionalities that I added to vizdat.

The following quotes are comments that were encoded and indicates some meta discussion.

vizdat!

Vizdat was built based on the user needs identified before. It offers an ecosystem for creating commenting with charts on the web. Building an extension was ideal since the idea is to modify web pages to allow charts to be rendered and add new elements to the comments sections.

Function list

• render visualization on page when links of vis are detected
• Allow users to reply with viz organically from the comments section
  • Reply with viz: loads the vis associated with that post to blend in with the Reddit UX
• Edit viz and reproduce vis in situ in the comments section (seamlessly)
• Have the data and vis in one resource if user clicks on the rendered interactive vis or links
• Edits include: change type, scale , colors, story , data type

Challenges 

Technical challenges

The first challenge I faced to address the needs on reddit, is a technical challenge.  R/dataisbeautiful only allows for text and images post, no code or markup could be embedded. Comments also are text only. Reddit users React which is a front end framework and they tend to have a weird behavior in layering pages. Also, the class and id names for their elements are random and the names can’t be tracked or selected. All of that made it so challenging to manipulate the DOM and actually have the extension render charts and buttons to facilitate commenting with charts.

However, with continuous iteration and testing I was able to build a tool that fits in well with the reddit community (vizdat is generic for all websites with discussions, but i had to customize the extension for reddit at some part of the UX).

Social and Moderation Challenges

Now that the tool worked, I tested it out in r/dataisbeautiful. The community is well known to be passionate about data visualization. I posted 3 posts and received very few interactions and I wasn’t able to put up instructions to use the tool, so the comments I ended up receiving weren’t using the tool. 

I reached out to the moderators for help but I was told advertising tools in the community is not recommended and could lead to posts being removed. The moderation on r/dataisbeautiful was challenging when it comes to research, specially that my tool is still in its testing phase and asking users to adopt a new tool requires more control over the type of posts (pinned post with instructions for example.)

In order to overcome that adoption and moderation challenges, I created a subreddit r/vizdat that simulates the rules and constraints of r/dataisbeautiful. The only difference is that I am the moderator and can easily mandate rules and keep posts. The goal of that subreddit is to usability test my tool. 

vizdat co-design and usability testing sessions

I tested the tool with 10 users, 2 in r/dataisbeautiful and 8 in the simulated community r/vizdat . Each user study session lasted between 60 to 90 mins. The sessions were on zoom and I asked users to share their screens, follow the instructions provided in the community and think aloud. Other than co-designing and usability issues, I was interested in the thinking process that users go through when looking at other charts and what kind of comments are enabled using this tool.

Users of the study were a diverse set of participants. 4 were data experts in their field (2 medicine, 1 linguistics, 1 clinical dietitian). They use analysis tools such as SPSS and sometimes Excel to manipulate their data. They create visualization using these tools and share them in their reports and papers. The other 6 participants were computer scientists who are comfortable with programming and technology but rarely visualize.

Results and Discussion

To my surprise domain experts did a better job generating charts with good stories than those who are computer scientists and tech savvies. It was easier for them to frame a narrative and then build a visualization. The limitation could be that the CS sample didn’t include visualization in their workflows and had difficulty story telling. When building vizdat I made sure it was easy enough for anyone to use. The idea is to have a visualization as a lightweight easy step in online discussion. This first pass of user study is more to tackle the usability issues. Some of the main issues were:

1- Some users never used Reddit in their entire life, this was one of the biggest issues. Posting on reddit is not intuitive especially if the subreddit had restrictions in commenting (only links and images allowed). I had to show them to reduce the learning curve.

2- Users who chose to visualize their own data shared their data cleaning process. While this is out of scope it was useful to see how these users were also struggling with their own current flows. Vizdat gives users the ability to do some data manipulation such as changing data types and so on.

3- Some users lack knowledge in info vis (e.g. representing nominal vs quantitative data) the tool was helpful for them in which it provides a cue of the data type. However, they need more than that, for example a help button and a tutorial to educate them in the basics of info vis.

4- Some users asked about the provenance of the data, the tool allows users to fork visualizations and data in order to create their own, while the forking feature was clear, users wanted to see the lineage of users before them.

5- the first batch of users were so helpful in framing my instructions. One user suggested having in the instructions two images one showing the community without vizdat and the other with the extension. Another one found it really useful to have the video with the instructions as opposed to reading text.

7- Most users like the feature in which vizdat automatically creates a starting chart based on the data they have uploaded. However, one user mentioned: “the auto viz thing primed me, i feel it affected my judgment to go with your suggestions.” That was when she created a post. It was a different case when she commented since it was clear what she actually wants to do.

8- Usability issues such as were to click to close a window and how to share were addressed in the final version shared in chrome store.

Future work

• I’m planning to follow through with the suggestion from the r/dataisbeautiful moderator. While he recommended not spamming the community he suggested reaching out directly to users in the community and asking them to post. That way I will make sure I’m recruiting a more relevant sample for my study.
• To scale and have a better sense and observations, I’m planning on starting a visualization GAME in r/dataisbeautiful (if the mods allow me). The game idea is to have a main post and as users to comment with another chart using the data but telling a different story. The last person in the game who successfully reproduces an interesting chart is the winner.
• On r/vizdat the simulated community. One user posted something NSFW see screenshot below. The way twitter works is that it doesn’t render any link or thumbnail if the post is marked as NSFW. However, vizdat renders any visualization link created with the tool. As a moderator and a tool builder, in my future work I will think about how to make sure a community is a  safe space even with the tool? One idea is to detect the word NSFW in the web document and not render.

Acknowledgment

I would like to thank Ethan for his continuous support and great advice during and before the class. I would like to thank Nathan Mathias for showing me the way on Reddit and the moderators. I would also like to thank Anna for her support and patience in replying to my questions. Finally, if it wasn’t for my advisor David Karger’s direction and his trust in my ideas, I wouldn’t have had the freedom to explore the “what-ifs” in research and online discussion.

Appendix

vizd.at

chrome plug-in

example on r/dataisbeautiful

r/vizdat