<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Madeline Welsh on Medium]]></title>
        <description><![CDATA[Stories by Madeline Welsh on Medium]]></description>
        <link>https://medium.com/@madelinebwelsh?source=rss-2be18f4905fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*AF4uBQWQL6lcMMQx.jpeg</url>
            <title>Stories by Madeline Welsh on Medium</title>
            <link>https://medium.com/@madelinebwelsh?source=rss-2be18f4905fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:26:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@madelinebwelsh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What Are Users Thinking When They Dismiss Notifications?]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/what-are-users-thinking-when-they-dismiss-notifications-f3e9f08b551b?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3e9f08b551b</guid>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Thu, 03 Aug 2017 14:38:05 GMT</pubDate>
            <atom:updated>2017-08-03T14:38:05.279Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Lessons learned from testing further actions and personalization in web notifications for the UK snap election.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yY5GTZdCAmQIWXTWd-tLJw.jpeg" /><figcaption>Photo by Daniel Sorabjidaniel / AFP/Getty Images</figcaption></figure><p>After the UK and US elections of 2016, the Super Bowl and Olympics, we thought we were likely done with notifications experiments here at the Mobile Lab. But 2017 has held its share of surprises, and one came in the form of the <a href="https://www.theguardian.com/politics/2017/jun/09/the-snap-what-you-need-to-know-election-results">UK snap election</a> held on June 8.</p><p>We decided to run one (likely last) notifications experiment. We had experimented with data on the UK’s constituency votes once before, <a href="https://medium.com/the-guardian-mobile-innovation-lab/web-notifications-part-2-auto-updating-259f45afa39a">around the E.U. referendum in May 2016</a>, and we also knew that the Guardian visuals team would be publishing an interactive, which we could work with as we did for our experiment during the US presidential election. For the snap election, we decided to experiment using some of the new image capabilities made available by Google to create a new type of web notification for Android phones. (Alastair Coote, a lab developer, <a href="https://medium.com/the-guardian-mobile-innovation-lab/generating-images-in-javascript-without-using-the-canvas-api-77f3f4355fad">recently wrote about the technical aspects</a> of Google’s expanded image formats.)</p><p>We built two types of web notifications: a live data alert with a “switch view” feature and a constituency alert that updated a user when the vote was called for a specific voting area to which they had subscribed. Both are described in more detail below.</p><h4><strong>Two types of alerts and what they looked like:</strong></h4><p>We have tested live data notifications <a href="https://medium.com/the-guardian-mobile-innovation-lab/four-key-takeaways-from-our-election-night-live-notifications-experiment-7a148ade899c">previously</a>, both as web notifications and through the Guardian iOS and Android apps. For our live data notifications for this experiment, we retained many of the previous features of the earlier notifications, including data visualizations within the notification, as well as the way they <a href="https://medium.com/the-guardian-mobile-innovation-lab/web-notifications-part-2-auto-updating-259f45afa39a">updated automatically</a>. We also added in a few new features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/403/1*4mvrUcngXyypyukuBR45_Q.png" /><figcaption>The two views of the national alert</figcaption></figure><p>First, we ran an alert for the national results, which contained live updating vote data. We ran it on the main Guardian domain, rather on than the Guardian Mobile Lab site, gdnmobilelab.com, off of which we had previously hosted our experiments with web notifications. This allowed us to serve a bigger audience and also to make the experience a more seamless one. The live data itself came from feeds set up by the Guardian visuals team, who built the full <a href="https://www.theguardian.com/politics/ng-interactive/2017/jun/08/live-uk-election-results-in-full-2017">live results page</a>, to which the alert was linked.</p><p>We added a new feature, which we called a “switch view.” When a user tapped the action button (one of two) labeled “Latest Declared,” the notification would flip to a second visualization of the most recent voting precincts to be called, shown in reverse chronological order. Tapping on the button again, now labeled “Back,” would show the user the initial screen of the overall tallies of the national results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/1*8W-uSe_-eP2PzEnGwYpSvg.png" /><figcaption>The constituency alert collapsed (left) and expanded (right)</figcaption></figure><p>In addition, we also ran a second type of notification which we called constituency alerts. (A constituency in the UK electoral system is a geographic area that comprises a voting bloc, somewhere in size between a voting district and a state in US politics.)</p><p>Users who accessed the <a href="https://www.theguardian.com/politics/ng-interactive/2017/jun/08/live-uk-election-results-in-full-2017">full live results page</a> (on either desktop or mobile) could subscribe there to receive a separate notification when the result of a certain constituency was called. Users entered the post code or first few letters of the name of the constituency and tapped subscribe. When the constituency was called, they would receive a result notification on the platform on which they subscribed.</p><h4><strong>What we wanted to know</strong></h4><p>For this experiment, we were looking for a few key insights to add to what we’d learned from previous experiments. First, we were looking for signals about the right level of alert customization by offering the constituency alerts. We were also looking for better ways to display data visualization in the national results alert. Alongside those, we wanted to know if people had an appetite for getting additional data-rich information in an alert, updating in real time, that was easy to switch to.</p><p>For the constituency alerts in particular, because they were so localized, we wondered if constituency-level information in alerts would resonate and be useful, and if there was an appetite to subscribe to that level of customized information.</p><h4><strong>How they did</strong></h4><p>We sent alerts to 20,172 subscribers. Of those, 57% of users were in the UK, followed by the US and Australia, reflecting the three primary countries the Guardian serves. Of these, 11,077, or about 54%, were on mobile. Of the total users, we know that about 20% (or 4,030) subscribed to the constituency alerts, while around 75% — 16,000 users — subscribed to the national live data alerts. That 16,000 number is slightly soft because we had multiple ways to sign up for the national alert, and users may have received them on multiple devices, which may mean a slight inflation of the number. The rest of this writeup will focus on the mobile user experience.</p><p>Following the alerts, we sent a survey through a notification. It was completed by 1,881 respondents.</p><h4><strong>What we learned</strong></h4><p><strong>More than half of our users engaged with the alerts at least once… </strong>For the national alerts specifically, more than half of the users proactively engaged with the alerts by switching the alert views or tapping the alert.</p><p><strong>…And of those who engaged, the average number of taps per user was nearly 15. </strong>We updated the alert each time the data feed registered a change, which amounted to several hundred updates over the course of the vote tallying. Those users who did engage tapped an average of 14.8 times each, on an average of 5.6 alerts over the course of the event.</p><p><strong>For this real-time event, more users signed up from the live results page than from any other method. </strong>This was a change. Historically, we have had three methods of recruiting users to participate in our web notification experiments: with an article written by the lab that goes up a few hours to a day ahead of the event; in a link in a related live blog; and via invitations on Twitter and other social media from Guardian US and other accounts. For this experiment, we were able to include subscription buttons on the Guardian’s live results page. We ended up gaining a majority of overall users from those buttons. It was also the only place users could sign up for constituency alerts, suggesting that perhaps keeping sign-up for live data alerts close to the data or event coverage itself is a strong recruiting channel on the day of the event.</p><p><strong>Users used the ‘switch view’ functionality built into the national alert. </strong>We registered 31,171 taps on switch views, or about 2 per user, 98% of which were on mobile. In our survey, 83% of users who said they had switched views also found the feature useful, though some did additionally note that, compared to a live broadcast on the BBC the alerts “felt slow.” Users who did use the switch view had overall higher alert interaction rates by about 10% as compared to other users.</p><p><strong>Users told us why they closed notifications: they had the information they needed. </strong>We’ve asked participants in a few previous surveys why they closed their notifications, and their responses have started giving us a clearer look at their motivations for closing an alert. Of the survey respondents who answered this question, 84% said they closed notifications because “they were informed and didn’t need it anymore.”</p><p><strong>Most of our national alert engagement came at the end of the votes being called, rather than at the beginning. </strong>Specifically, the vote totals for the last five seats to be reported, versus the first five seats, prompted the most engagement. Taps on the national alert updates for the final five seats accounted for 17% of all of the national alert updates that were interacted with, while taps on updates to the national alert for the first five seats accounted for 7%.</p><p>Local time likely played a role here: the first seats were called in the UK starting at around 10:30pm GST, relatively late in the evening when users may have been asleep, whereas the final seats were not called until the following afternoon GST.</p><p><strong>We confirmed that adding the time the results were refreshed to these alerts, something users had told us previously they wanted, made the alert functionality clearer. </strong>After previous experiments, subscribers told us they would have liked to know how recently the results had been updated. We added a language that said “seats declared as of…” and a timestamp as way to indicate this. In the survey, users told us it was clear the alerts were live updating (to the tune of 94%), and 45% said it was specifically because of the language we added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/0*O-Xwi7f76-5tOOWi." /></figure><p><strong>Users are curious. They will press all the buttons. </strong>One somewhat extraneous observation, but one that we like: In building web notifications, one action button is always dedicated to accessing the browser’s settings, even though that button is unrelated to our experiment. People pressed it anyway. 70% of survey respondents who said that they had pressed it said they were just looking to see what it would do.</p><p><strong>Longform responses to the survey yielded some trends. </strong>We’ve written about them before, but much of our analysis is made possible by the great work of Maass Media. On our behalf, the Maass Media team has experimented with applying an NLP algorithm to analyze the sentiment of the freeform survey responses from users. The results were interesting.</p><p>The majority of positive responses were about the efficacy of live alerts, particularly from users who said they would not have been able to access the data as easily without our notifications. The majority of the negative responses were about about our users’ perception that our alerts may have caused their browser to crash. While it’s unlikely that the alerts caused large scale crashes, and there could have been many other issues contributing to performance issues people saw on their phones that night, including individual connectivity or by receiving an unusually high number of alerts.</p><p>This NLP work was buoyed by the fact that it is reusable for similar experiments. For their analysis of the survey responses for this experiment, Maass Media reused the algorithm from a previous notification experiment, based on words they had already coded as having positive and negative sentiments, and then re-applied the algorithm to these new responses. Having a reusable algorithm makes the upfront work of setting it up longer lasting, which may help newsrooms decide to take the plunge.</p><p><strong>That said, when asking for qualitative feedback from users, consider where you want to invite open ended insights. </strong>We included more freeform “other” response options than we had in previous surveys, and were left with an unintended dilution of insights from a few questions. For larger events, the crispest surveys with the most actionable results pose required questions that offer specific options for feedback.</p><p><strong>Constituency alerts provided a local look at the elections data. </strong>About 25% of our overall users signed up for a constituency alert. Users could sign up to find out when specific precincts were called and the results. 76% of survey respondents who said they signed up for a constituency alert said they found it useful, while 85% said would definitely or maybe sign up for it again.</p><h4><strong>In closing</strong></h4><p>As mentioned above, this will likely be our last notification-specific experiment. We’ve learned a lot, and will be working to distill these learnings over the coming months as we experiment with other forms of mobile storytelling.</p><p>For now though, <strong>we’ll take a second to extol the benefits of increased personalization in notifications</strong>. As each of our notification experiments has shown, if you provide users with an easy sign-up for a subject of notification, an equally easy way to opt out, and a functional layout, live and event-specific notifications are a useful and appealing way to connect users to real-time data and information. Furthermore, asking users to input specifically what they are looking for can be an important way to make them feel connected to their news organizations. (With only one sign-up point, over 4,000 users signed up for constituency alert specific to a post code, a seriously granular level of information!)</p><p>As new technical capabilities arise, there will be better ways to directly prompt users to ask for what they want. We hope our experiments show that users will be ready if only we will meet them there.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3e9f08b551b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/what-are-users-thinking-when-they-dismiss-notifications-f3e9f08b551b">What Are Users Thinking When They Dismiss Notifications?</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do We Build a Better Recommendation Experience for Mobile News Readers?]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/how-do-we-build-a-better-recommendation-experience-for-mobile-news-readers-b3ada44a4c5f?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3ada44a4c5f</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[consideration]]></category>
            <category><![CDATA[personalization]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Mon, 10 Jul 2017 18:32:40 GMT</pubDate>
            <atom:updated>2017-07-10T18:32:40.275Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>And why are offline reading apps still so stodgy?</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AZfwbxnlIo6Jgr6wVDh10w.jpeg" /><figcaption>Photo by <a href="https://www.flickr.com/photos/hernanpc/">Hernán Piñera</a>, used under a Creative Commons license</figcaption></figure><p>For subway commuters, it’s a common enough situation: you get on the train, pull out of the station and…ugh, you’re offline. On your phone: yesterday’s tweets, maybe a news app loaded up with old stories, a newsletter with links you can’t open.</p><p>Although many news apps now enable offline reading, they don’t ensure that the things we have access to offline are relevant to us as individual readers. I can get content offline from a news app on my morning train ride, but when I pull out of the station, I have no guarantee that what it will have served me will be relevant to my interests, in a format I like, or something I can reasonably read in the the time I have left in my commute.</p><p>At the mobile lab, we think there is space to push past what currently exists for offline reading, particularly where it intersects with the burgeoning area of content recommendations. To do this, we’ve looked at what exists for each type of experience and tried to identify the gaps and opportunities.</p><h4><strong>What’s out there now for offline news apps:</strong></h4><p>There are a few ways to get news offline currently: through the apps offered by news organizations, and through other apps that provide a way to access previously stored links from across the internet.</p><p>So far there seem to be two models for how offline news reading is offered:</p><ul><li>The first: download all the stories from a given news app at once, without preference given to what they are and how much time you have.</li><li>Second: have a separate app that holds all the stories you have collected to read from across the web.</li></ul><p>Many major news apps, as a form of efficiency, download and cache some or all of the app’s stories when the app is connected to wifi or cell signal. While not specifically a feature intended with the goal of making offline reading easier, some nonetheless have this function. You get the full sense of what the news organization considers important that day, akin to what they put on their home screen, even if you only read a fraction of what you’ve downloaded.</p><p>The other method, popular through apps like Pocket or Evernote, is to have the user do the work upfront by saving, or “pocketing,” links from across the web as they see those that interest them, and then pulling them up for offline reading later. Creating the link collection is incumbent on the user, and doesn’t enable further discovery, of the “Hey, you saw this, we think you might also be interested in this” variety. With apps like Pocket, what you saved is what you get.</p><p>One interesting product we saw was News.me, which unfortunately <a href="http://blog.news.me/post/34240501070/whats-next-for-newsme">shut down</a> in 2013. It <a href="https://techcrunch.com/2012/04/22/read-offline-news-me-automatically-downloads-your-news-whenever-you-leave-home/">contained an iOS app feature called Paper Boy</a>, which incorporated elements of your commute into your reading experience. When a user left a location they had designated in the app as their home, a reading package, pulled from what that users’ contacts were reading on Twitter, would be downloaded to their phone.</p><p>We were fascinated with this product for the ways it made use of mobile location data and also sought to address the issue of timing: Paper Boy was attempting to send readers a package of information they wanted, before they remembered they would want it.</p><p>For now, it seems that what’s out there are good initial options for the most basic prompt: I want to read offline. But when the prompt is adapted to: I want to read news<em> that is relevant</em> to me while offline, it’s clear that the available options fall short, and that without significant upfront investment of time (in the form of finding content yourself and saving it) there is no solid guarantee of having relevant content available for offline reading.</p><h4><strong>What’s the state of content recommendations right now:</strong></h4><p>Right now, while some news organizations are working on content recommendations, standalone services that include recommendations are trying to do that work of surfacing similar or relevant content for users in a few ways, according to what can be known about them.</p><ul><li>The first, content recommendations can come from your social graph — your contacts and friends lists — which an app can ask for access to.</li><li>Second, some apps offer the option to subscribe to topics during onboarding, or to follow a topic or author within stories you are already reading, so they can send future content based on those categories.</li></ul><p>Content recommendations might come from an app, such as Nuzzel, that asks for access to your contacts or friends list to show you things you might like to read based on what they’re reading. Or recommendations might come from allowing the user to create playlists of content, as on the podcast app Stitcher, then sending them content popular with users who selected similar content.</p><p>In another method, a user can follow a series or an author, and receive a notification the next time the person or series followed is published. This feature is available in the Guardian’s apps. Other news sites have been lightly experimenting with content recommendations for years: The New York Times’s “Recommended for You” section, available on desktop and mobile web, shows logged-in users a selection of articles they have not read. The Times has also <a href="https://www.nytimes.com/2017/03/18/public-editor/a-community-of-one-the-times-gets-tailored.html">announced a new initiative</a> to surface relevant, personalized news to each user.</p><p>Content recommendations also factor into a growing conversation about developments in artificial intelligence and its potential role in the newsroom. The discussion has addressed how AI and machine learning can be used to, for example, automate financial market stories or make comment moderation more efficient, as <a href="https://blog.google/topics/journalism-news/ai-newsroom-whats-happening-and-whats-next/">this post </a>by Erica Anderson, partnerships manager at Google News Lab, lays out. Another exciting potential use for AI: better content recommendations requiring less explicit upfront work from the user.</p><p>But what’s missing from these content recommendation methods now is that they don’t live up to the promise of giving readers content clearly keyed to their interests. A product based largely on a user’s manual preferences as they have indicated them is interesting, but limited. What if the user could access a set of recommendations, each of which would be relevant, through doing nothing more than simply consuming news as they would normally, allowing a recommendation engine to begin to “learn” more about the user?</p><p>While using my social graph provides a good look at the types of topics my network is interested in, it can fail to understand the nuances of my personal interests. For example, the fact that I follow friends who tweet about sports doesn’t give my preferred news organization any signal that, while I enjoy basketball stories, I don’t enjoy baseball in quite the same way. My reading history — lots of more basketball stories versus few baseball stories — might provide just that level of information. Similarly, while the ability to receive stories based on playlists I have custom created will ideally give me additional selections that reflect my interests, the results won’t appear without a significant initial investment in setting up my preferences.</p><p>Further, elements that news organizations could actively track and recommended against could help produce a better selection. Yahoo News Digest, another recently shuttered product that offered a package of stories (the content was not personalized) asked a user when they want to receive the briefing. Instead of asking “when do you want this,” what if Yahoo asked, “when do you want this and how much time do you have to read it?” Reading time then becomes another element of the recommendation. Using various signals from their mobile phone, we might be able to gauge how much content a user would prefer and add that to what we know about them.</p><h4><strong>We think there’s space for innovation here especially when applied to a specific use case:</strong></h4><p>The integration of content recommendations and offline reading would be particularly useful when you think about the original use case of commuting. While they do a good job of keeping content you’ve bookmarked in one place, none of the most popular offline reading apps, like Pocket or Newsify, have created a flexible, optimal offline news-reading package for individual users, nor do they include elements of personalization gained from the variety of signals from people’s mobile devices.</p><p>And on mobile, the benefits of this merger become even more clear. By integrating elements of personalization, gleaned from a user’s reading history, as well as location, and timing the delivery to when they might need the offline package ready, we think there’s an opportunity to make offline reading more lively, relevant, accessible and transparent to users, as well as a more complete experience.</p><h4><strong>What we’re thinking about now:</strong></h4><p>We’re in the midst of building an experimental product that explores some these opportunities, and are now thinking a lot about how we will measure engagement. For this product to be successful, we need to understand the correct signals that tell us which types of articles a user would like to see more 0f.</p><p>In addition we’re also looking at the problems that have plagued personalized products before: how do we get users to sign in, and how can we best be transparent about what data we are gathering? How do we give people personalized content without also making them feel they might be missing out on other news? What can we do to put users in control of what they are seeing without feeling overburdened by the need to constantly maintain their settings?</p><p>We’ll have more news about this experiment and a way for you to sign up soon.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3ada44a4c5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/how-do-we-build-a-better-recommendation-experience-for-mobile-news-readers-b3ada44a4c5f">How Do We Build a Better Recommendation Experience for Mobile News Readers?</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Live Updating Notifications: What We Learned From Reusing the Format for the Super Bowl]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/live-updating-notifications-what-we-learned-from-reusing-the-format-for-the-super-bowl-ca75184a30c8?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca75184a30c8</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[notifications]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 16:26:19 GMT</pubDate>
            <atom:updated>2017-04-04T16:26:19.413Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Users found alerts updated with scores and commentary useful — more so than a single alert at the end of the game.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4a70RJHNDq3bWFC9s8pwuQ.jpeg" /><figcaption>Super Bowl LI, between the Atlanta Falcons and New England Patriots, was played in Houston, Tex., on February 5, 2017. (Photo by Adrees Latif/Reuters)</figcaption></figure><p>After the success of our <a href="https://medium.com/the-guardian-mobile-innovation-lab/four-key-takeaways-from-our-election-night-live-notifications-experiment-7a148ade899c">live updating election notifications</a> last fall, we were eager to find a way to test this type of data-filled notification again for a different type of news event. So we thought, what about the Super Bowl?</p><h4>Why We Did It</h4><p>In addition to wanting to follow-up on the election notifications, we saw the Super Bowl as another large planned news event that provided a good opportunity to test the formats on a lighter topic. We have wonderful sports editors here in the US who have live blogged the game for the past few years. (For readers outside the U.S., the Super Bowl is the final game in the National Football League’s annual calendar and a huge event for many Americans.) We thought that a live data alert sent from the Guardian might pique users’ interest. We also had collaborated well with the US sports desk previously for the Olympics, and for some of the lab’s earliest experiments.</p><p>A notification that combined data and commentary would, we thought, provide an informative and accessible way to get live information, including scores and plays. Further, we thought the live commentary through notification would be a way to differentiate our alerts from news alerts, which would likely only cover kickoff and the outcome of the game, as well as alerts from sports apps, which were likely to be even more data driven.</p><p>Finally, building this notification experience was a way to test and fulfill user interest in more of these kind of alerts. Following the elections notifications, 46% percent of users had told us that they might be interested in live updating notifications around sports.</p><h4>Our Hypothesis</h4><p>We believed that the appetite for live data we had identified through the elections alerts would be persistent in other kinds of events, and would resonate especially with a sports-focused audience. We thought we would see this in how users rated our alerts as useful or interesting, and in how they close, expand, and tap through on the alerts.</p><h4>What We Did</h4><p>For the Super Bowl, we worked with the UK apps teams to build a live updating alert into the Guardian iOS and Android apps that provided live scores and commentary during the game, updated by the Guardian US sports desk, with whom we developed the idea for what we would offer. The notification was designed to provide users with a way to stay up to date by glancing at their phone, while having the option to tap through for more information, much the same as in the election notifications.</p><p>We promoted the alert both in the US and globally through a sign-up screen that was shown to both iOS and Android Guardian app users in the US, as well as Android users globally, to notify them about the availability of the notifications and specifically target those who had previously read a Guardian story about football. From the screen, users could tap to sign up for the notifications. Android users were also able to sign up through their app settings.</p><p>We also worked with the sports desk including sports editors Tom Lutz and reporter Bryan Graham, as well as Sam Morris, a designer, to develop a live scoreboard graphic that would be included in the expanded notification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*TBkBNaqs1hZnnnncbV1ovw.png" /><figcaption>Collapsed and expanded views of the Super Bowl notification formats on iOS (left) and Android (right).</figcaption></figure><p>Unlike in the election notifications, which also featured an automatically updating graphic with electoral vote totals in the expanded view, populated by a feed of AP data, the Super Bowl scorecard was updated manually by Bryan during the game. He was able to change the score and write in his commentary easily throughout the game using a tool created by lab developer Connor Jennings. In the expanded view of the notification, we offered a button to tap through for the live blog, as well as a Stop Updates button, which ended the notifications and unsubscribed the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvrQSd2u3ZFUpkS8Vet__Q.png" /><figcaption>The tool used to update Super Bowl alerts, showing previews of the collapsed and expanded notifications.</figcaption></figure><p>We sent notifications during the first half of the game, took a break for half time, and then resumed for the second half. Our final notification was sent immediately after the Patriots scored their final touchdown during the very surprising and historic overtime. We sent a notification at noon ET the next day with a survey link asking users for feedback on the experience, as we do after every experiment.</p><h4>Numbers in Brief</h4><p><strong>Audience Size:</strong> 6,923 users total</p><ul><li>4,126 on iOS</li><li>2,797 on Android</li></ul><p>20 alerts sent over the course of the game</p><p><strong>Engagement:</strong></p><ul><li>10% of users who saw the sign-up screen opted-in to the alerts</li><li>Users expanded the alerts an average of 10 times each over the course of the game</li><li>On Android, one third of users tapped through to the live blog around twice. (Unfortunately, iOS data was unavailable.)</li></ul><p><strong>From the survey:</strong></p><ul><li>Users who said the commentary was useful, easy to read, or a good complement to live score information: 91%</li><li>Users told us it was clear or somewhat clear that the alert updated : 90%</li><li>Users who said they felt they were kept up to date or very up to date by the alerts: 79%</li><li>Users who said they would definitely or maybe sign up for these alerts again: 94%</li></ul><h4>The Data Told Us</h4><p><strong>The conversion rate from sign-up screens to alerts was about 10%. </strong>The total number of people who saw the sign-up screen was about 63,000, of which about 6,900 opted in, for a conversation rate of just over 10%. For contrast, the conversion rate for the US presidential election night live data notifications was higher, at 37%.</p><p>Some possible reasons for the disparity: First, the US presidential election was a global event that also commanded a larger audience overall at 230,000 users. Additionally, the Super Bowl sign-up screen was slightly different between iOS and Android versions, and also between the US and global audiences, which may have had an impact on the overall number of sign ups. In the future, we would want to make the sign-up experience more consistent for users on both platforms. As well as being good practice, it will also help us to get a better sense of the analytics across both platforms.</p><p><strong>Users expanded the alert about 10 times during the course of the game. </strong>On average, users expanded about 10 of the 20 alert updates we sent. Of users who took our follow-up survey, 79% told us that they thought the notifications were a good way to stay up to date. One of the goals of our experiments has been to enable user choice. With that in mind, we didn’t expect to have a 100% expand rate on all alerts. We wanted to make sure the user felt informed and could get more information when they chose.</p><p><strong>Users liked the combination of scores and live commentary in the same alert. </strong>In the survey, 78% of users who expanded the notification said they found the combination of scores and live commentary interesting or very interesting, and 79% said this combination was useful or very useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*VuRMkOQceCbSPPAe." /></figure><p><strong>The majority of users found the scorecard helpful and easy to use, while about half of users said it gave them the information they wanted. </strong>In our survey, users gave varying reviews of the scoreboard: 66% said it was useful; 70% said it was easy to use; and 51% said it gave them the information they wanted. Only a few users — around 3% — said the alert was not useful to them.</p><p>In planning the scoreboard graphic we had two of Sam’s designs to choose from: one that showed which team had possession along with the score, and one that just had the score alone. We ultimately chose the latter: because Bryan was updating the score manually, indicating possession, which fluctuates more rapidly, would have introduced another layer of complexity that we weren’t sure we were staffed to handle. Additionally, this choice meant the Guardian US audience team, for whom Sam had also created the designs, could more easily use the scoreboard alone as Twitter cards.</p><p>In our survey, users said they might have liked that information about the team in possession (54%) or a visualization of the game statistics (41%), which we would like to work on for future iterations.</p><p><strong>When users dismissed an alert they said they were doing so because they ‘got’ the information, not because they didn’t like it. </strong>We’re particularly interested in what users do with information in an alert when they don’t immediately tap through. When they clear or dismiss a notification, what are they saying? We asked users what it meant when they cleared a notification and were excited to see that the answer wasn’t that they were unhappy, but rather they had received and consumed the information provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*N7NbNc4w8D9JVcVh." /></figure><p>We saw a very small opt-out rate of less than 10% on both platforms, while 77% of users told us that they knew how to opt-out. While we were unable to track when in the course of our experiment users opted out, most survey takers told us that if they did opt-out, it was because the game was over, not because our notifications had become burdensome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/0*vdeoMUur00pWIU29." /></figure><p><strong>Gut check: 95% of survey takers told us that these alerts were more useful than a single alert at the end of a Super Bowl. 94% of users said they would sign up for them again.</strong> That’s pretty good!</p><h4>Additional Insights</h4><p><strong>Our general hypothesis — that a sports-focused audience would have an appetite for live updating alerts that include data and commentary — was proven. However there were fewer tap throughs to live content than we had seen in previous experiments. </strong>We had a few technical issues throughout which meant that users, particularly on iOS, did not receive all the notifications, which likely depressed the tap-through number.</p><p>The lower number of tap throughs may also be due to the more visual nature of the Super Bowl. Our users told us that on the whole they were also watching the game on television, which would have served as a primary means of information. We were offering brief analysis at a glance, but to further engage with that analysis would have required users to switch their attention to actively read about the game with slight delay, rather than watch it live.</p><p><strong>Running this type of experiment required a fair amount of advance preparation work, as well as the work of an editorial staffer on the day.</strong> We started work with the apps teams in the UK on these notifications two months prior to the Super Bowl, to ensure their availability in the Guardian apps, a process that required a lot of focused communication. And because these alerts were manually sent during the game, there needed to be editorial resources attached to them during game time.</p><p>We were very happy to work with Bryan and think the notifications benefitted greatly from the amount of nuance and familiarity with the subject matter he was able to put into the live commentary. Without his contribution the experience notifications would not have been as conversational, informed, and quickly delivered.</p><p><strong>We’re still thinking about the question: What is a complete experience in a notification? </strong>And <a href="https://medium.com/the-guardian-mobile-innovation-lab/analysis-without-benchmarks-an-approach-for-measuring-the-success-of-innovation-projects-6803ca8ddd9d">another question we’re exploring further</a>: what is a positive interaction with a notification and how do we better analyze that experience? It’s clear that notifications hold a lot of power, even in the small space in which they appear. Figuring out how to make a complete experience of them, though, is still clearly a very subject-specific task. For now, it is useful to have evidence that, for an intensely visual event such as the Super Bowl, users will have different needs and demonstrate different expected behavior than that of a less visual event, like the election. Watch this space for more thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca75184a30c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/live-updating-notifications-what-we-learned-from-reusing-the-format-for-the-super-bowl-ca75184a30c8">Live Updating Notifications: What We Learned From Reusing the Format for the Super Bowl</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What We’ve Learned (So Far) From Building and Testing ‘Shifting Lenses’]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/what-weve-learned-so-far-from-building-and-testing-shifting-lenses-f46ad0ddabc6?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/f46ad0ddabc6</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[live]]></category>
            <category><![CDATA[breaking-news]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Fri, 17 Mar 2017 16:38:56 GMT</pubDate>
            <atom:updated>2017-03-17T16:49:46.118Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Users sent strong signals that alternative views of of live coverage make sense to them.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*g_LMs1-w40fMc_3ymJwwDA.png" /><figcaption>On the podium, Off the podium lenses on inauguration day</figcaption></figure><p>With two recent projects using a new format we’re calling “Shifting Lenses,” the lab is now moving into experimentation on live coverage, a <a href="https://medium.com/the-guardian-mobile-innovation-lab/five-proposed-areas-of-focus-for-mobile-innovation-in-news-1545f8da2528#.ivx67by1v">second area of focus</a> that we outlined at the start of our time here. The feature, a proof of concept that we’ve <a href="https://medium.com/the-guardian-mobile-innovation-lab/shifting-lenses-a-first-look-what-a-mobile-centric-live-blog-could-be-7eae9a3a634b">written a little bit about before</a>, is an initial pass at a mobile-first reworking of the live blog format. It includes two different views, or “lenses,” through which a user might better understand or follow a live event.</p><p>We’ve now tested the feature during two events and are excited to share some of what we’ve learned from running it during the inauguration and the Super Bowl.</p><h4><strong>Why We Did It</strong></h4><p>Shifting Lenses came out of work we did with <a href="http://www.codeandtheory.com/">Code and Theory</a>, a New York-based digital agency, to design and prototype mobile-first features for live news coverage. In an <a href="https://medium.com/the-guardian-mobile-innovation-lab/shifting-lenses-a-first-look-what-a-mobile-centric-live-blog-could-be-7eae9a3a634b">article</a> published just before our first test of the feature during the inauguration, we talked a bit about some of the thinking and research about the current state of live blogs that went into development of the feature.</p><blockquote>“Last year, at the start of the lab, we started thinking about how live coverage could better suit a mobile-first era, and noticed how little had changed since live blogs became a popular format used by a large number of news organizations, in a pre-smartphone era. We looked at lot of live blogs covering a variety of news events and noticed they shared a number of <a href="https://medium.com/the-guardian-mobile-innovation-lab/reimagining-the-live-blog-as-a-mobile-first-experience-e50d72f2197#.qds6zw89a">common features</a>, ones that make them ill-suited to modern mobile reading habits.</blockquote><blockquote>First, there’s currently really only one way to move through most live blogs — from the most recent update to the oldest. This organizational principle matters when you consider all the different times readers may be entering a live blog. There are very few clues as to what has happened prior to the first update they see (usually the most recent) and what the latest post means in the context of others. That most recent post might build on a narrative thread the blog has been following for some time, or introduce a new topic, or correct an earlier assumption. The reader is left to decipher for themselves how it fits into the whole.</blockquote><blockquote>Second, and most relevant to this experiment, a live blog doesn’t consider that a user might find some information in the live blog more interesting or more useful than other pieces of information. For example, some users may prefer maps or other visual elements to text describing a location. These limitations are compounded on mobile where reading a live blog can feel like an exercise in endless scrolling.”</blockquote><h4><strong>Our Hypothesis</strong></h4><p>We believed taking advantage of the ability to swipe to a new screen on mobile devices could help users to better keep up with multiple lines of coverage during a live event. We predicted we would see signs of its effectiveness in how users interact with the lenses and through the users’ affirmation that they understand the format type.</p><h4><strong>What We Did</strong></h4><p>Shifting Lenses was built to address dual concerns about how well (or not) live blogs are organized to make storylines clear and scannable. While a live blog usually covers the whole of an event, multiple storylines often coexist within it, and we thought that teasing out these lines would better direct readers towards the parts of the coverage they were most interested in. To do this, we created two views for each live blog — the namesake “lenses” through which users might understand an event.</p><p>Because we were building these features to test around planned events, we gave some thought ahead of each event about what storylines would emerge. In the case of both the inauguration and Super Bowl, we realized the different storylines had a lot to do with the concept of proximity to the main event. We realized that users looking for updates might not just be looking at the main event, but also on what was happening around it.</p><p>Here’s how we thought it through: For the inauguration, readers might visit the live blog for the inaugural ceremony, as well as for news on all the other events going on around it, like reactions from the crowd and the protests. For the Super Bowl, some readers would want game updates, just as others would be interested in the surrounding spectacle — the ads and the half-time show.</p><p>For the inauguration, we called the lenses were “On the podium,” and “Off the podium.” The “On the podium” lens was made up of live blog posts which covered official and pre-planned events. These included the arrival of notable politicians, the inaugural address, and the departure of President Obama. The “Off the podium” lens included live blog posts describing what happened around the inauguration, like the protests that broke out in Washington DC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*eqLBkAu9HBHwbr1e4x_kiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*IJDdTuBSDzJ_B83dNTzjKQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*u7L49yx0M0-lv33j3GFQ9A.png" /><figcaption>On the field, all post, and ads and half-time lenses for the Super Bowl experiment</figcaption></figure><p>For the Super Bowl, our two lenses were “On the field” and “Ads and Half-time.” The Guardian actually published separate live blogs for these two storylines, so our task became simply to juxtapose them for viewers interested in one or both lines of coverage.</p><p>To create the two lenses, mobile lab developer Alastair Coote used the Guardian Content API to pull in content from the live blogs. He also used the Twitter and YouTube APIs in order to display media embedded in the Guardian live blog posts. For the inauguration day test, these posts were pulled into a tool where another member of the mobile lab was able to decide which posts went to each lens. During the the Super Bowl test, the separate live blogs for sports and entertainment coverage meant that the lenses could be automated. All posts were sent directly to the respective view. In each test we also included a middle view between the lenses that included “All posts” so users could choose to view all the posts at once.</p><p>For these first tests, we ran Shifting Lenses on a delayed schedule to test the workflow behind it. On inauguration day, in order to test the workflow of the feature as much as what it looked like to an external audience, we did not attempt to run it as a real-time feature, and ran it hours into and after the day’s events. The audience sizes for these first few tests reflect the delayed launches.</p><h4><strong>Numbers in Brief</strong></h4><p><strong><em>Inauguration</em></strong></p><p><strong>Audience Size:</strong> 119 users</p><p><strong>Engagement:</strong></p><ul><li>1,819 total scroll starts, or an average of 9 scroll starts per user</li><li>341 total swipes between lenses, or an average of 1 to 2 swipes per user</li><li>141 total taps to move between lenses, or an average of 0 to 1 tap per user</li></ul><p><strong><em>Super Bowl</em></strong></p><p><strong>Audience Size:</strong> 521 users</p><ul><li>98% of users were on mobile</li></ul><p><strong>Engagement:</strong></p><ul><li>11,693 total scroll starts, or an average of 22 scroll starts per user</li><li>1,895 total swipes between lenses, or an average of 3 to 4 swipes per user</li><li>404 total taps, or an average of 0 to 1 tap per user</li></ul><p><strong>Combined responses from the Inauguration and Super Bowl surveys:</strong></p><ul><li>Users who said the format was easy to use: 95%</li><li>Users who said the different lenses made sense: 90%</li><li>Would maybe or definitely sign up again: 94%</li></ul><h4><strong>What the Data Tells Us</strong></h4><p><strong>Users swiped much more than they tapped to navigate between the lenses. </strong>Both tests show that swiping far outperformed tapping as a means of “shifting” between the lenses, by a ratio of four to one. The prevalence of swiping shows that users generally understood how to navigate through the lenses.</p><p><strong>Users said the feature was easy to use. </strong>In surveys for both tests, users said by a wide margin that the feature was either very easy or kind of easy to use, further supporting the idea that a mobile-first navigation paradigm could work in an adapted live blog. All of those who were surveyed for the inauguration said the feature was easy or kind of easy to use, a figure complemented by the 90% of those who said the same in their answers to the survey for the Super Bowl experiment.</p><p><strong>Users understood why we separated these storylines and the choice of lenses made sense to them. </strong>Users also said the way we broke out storylines was clear in motive and presentation. 90% of users surveyed said the inauguration day “One the podium” and “Off the podium” breakouts made sense and were useful to them, as did 90% of the Super Bowl users surveyed about “On the field” and “Ads and Half-time.” Users from both tests also said that they could see using the format for news cases different from the one they had seen. 80% of Super Bowl users said that they would be interested in the Shifting Lenses format for political events and 60% expressed interest in it for breaking news.</p><h4><strong>Additional Insights</strong></h4><p><strong>This proof of concept seems to resonate with users. </strong>These first two tests suggest that users would be interested in seeing future development of this format type. In the future, to continue to test this feature, we will need to test the workflow of Shifting Lenses for a truly breaking news event and try to update it in real time.</p><p><strong>Editorial assistance (possibly) needed. </strong>As noted earlier, the idea behind Shifting Lenses was to break out specific storylines. In the case of the Super Bowl, the Guardian US newsroom had already decided to cover the event from two angles: sports as well as the ads and entertainment. This made putting together Shifting Lenses an exercise in addition. We were taking the two live blogs and connecting them side-by-side for the same event.</p><p>In the case of the inauguration — and, we think, any future live or breaking news event — creating Shifting Lenses becomes more of an exercise in division, separating out the different lines of coverage from an ongoing stream of incoming information. This process leads to the same type of user experience, but requires a different, more editorially dependent workflow to make the judgements about which lens each live blog post belongs to.</p><p>We think it’s premature to say if one flow is better than the other, and the answer may prove to be completely context-dependent. What we can say thus far, though, is that the format needs editorial influence up front to decide the topics of the lenses, and to distill the narratives each lens will follow.</p><p><strong>Next steps: User feedback from the survey suggests we might want to send clearer signals, or include more prompts for how to view the different lenses.</strong> They suggested we think about a way to indicate that there is content that exists to the left and right when scrolling down the page.</p><p>We’ll continue to explore the possibilities for altering live coverage to better suit mobile users looking for news where they are.</p><p>Let us know what you thought of these experiments or share ideas to <a href="/service/mailto:innovationlab@theguardian.com">innovationlab@theguardian.com</a> or on Twitter @gdnmobilelab.</p><p>To follow future live coverage experiments, <a href="https://itunes.apple.com/us/app/guardian-mobile-innovation-lab/id1194055480?mt=8">download our iOS app</a>.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f46ad0ddabc6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/what-weve-learned-so-far-from-building-and-testing-shifting-lenses-f46ad0ddabc6">What We’ve Learned (So Far) From Building and Testing ‘Shifting Lenses’</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Live: Now From Your Lock Screen]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/live-now-from-your-lock-screen-532133e22419?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/532133e22419</guid>
            <category><![CDATA[live-streaming]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Tue, 14 Mar 2017 21:35:41 GMT</pubDate>
            <atom:updated>2017-06-29T17:31:32.253Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Users watched live video in an expanded notification for an average of three minutes.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*1t6ZA7dTxcrnGUJuc6vVvw.png" /><figcaption>The Guardian Mobile Innovation Lab’s live video within an alert on January 20, 2016.</figcaption></figure><p>Even now, in an era that feels saturated by breaking news, live video has a startling power to transport the viewer into the action. When we talk about events after they happen, we now say not only “Do you remember where you were when…?” but also “Do you remember what that looked like?”</p><p>Newsrooms have a variety of ways of making live video available on desktop, but fewer means of directly bringing users into a live video stream on mobile. For the inauguration on January 20, we tested a completely new format that offered an additional entry point: live video inside a notification, sent to iOS users via the Mobile Innovation Lab app.</p><h4>Why We Did It</h4><p>An ongoing goal of the mobile lab is to investigate how notifications can be used in new ways to provide both utility and context for the user. By adding a live video stream to a notification, our aim was to offer a totally new entry point for mobile users who may want to know what’s going on “right now” or who may want access to the source material (like a live view of an official statement, ongoing protest, or major event).</p><p>We were interested in using the inauguration, with its hours-long duration, to see when users would open a live stream, how long they would watch for, and if they would re-engage at different points during the day. Would users expand to watch for just the major events or would they use the stream as an alternate television?</p><p>This was also an opportunity to do something brand new. We believe this was the first use of live video in a notification ever — an exciting first and an opportunity to break ground and evaluate the format for future use.</p><h4>Our Hypothesis</h4><p>Our belief in creating this format was that by making live streaming video of an important news event more accessible on mobile phones while news is happening, live video notifications would offer mobile users a level of convenience they wouldn’t otherwise get by seeking it out on TV, a desktop web page, or within an app.</p><p>We saw possible indicators of success of the format as time users spent with the notification expanded and the video playing, as well as positive feedback to our survey questions about its usefulness and functionality.</p><h4>What We Did</h4><p>We recently launched an <a href="https://itunes.apple.com/us/app/guardian-mobile-innovation-lab/id1194055480?mt=8">iOS app</a> for the purpose of running Mobile Innovation Lab experiments quickly and easily. One of the lab’s developers, <a href="https://medium.com/@_alastair">Alastair Coote</a>, <a href="https://medium.com/the-guardian-mobile-innovation-lab/the-hows-and-whys-of-building-the-guardian-mobile-innovation-lab-app-594f674a0dbe#.c33al0jl0">who built the app</a>, included the capacity to send live video notifications. The notifications were available to users who downloaded the app and allowed them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/265/1*nwGyHUHitfI6Cl7l3tmyhQ.gif" /><figcaption>Expanding the notifications</figcaption></figure><p>To populate the notifications, we relied on the Reuters live video feed, which we knew would have live coverage of the entire inauguration day and the attendant events. The notifications were sent from a tool, created by <a href="https://medium.com/@cojennin">Connor Jennings</a>, the other lab developer, and run by the mobile lab, which allowed us to include a notification title and bit of text, updated continuously with what was happening in the live video.</p><p>Our first live video notification was sent at 11am EST, as members of the president-elect’s family and politicians arrived at the ceremony in Washington DC. It also included instructions to “press and hold to expand the notification.” In later pushes, we changed this language to “press and hold, or swipe left to view” after users on older model phones, where the press and hold to view was not applicable, told us on Twitter that our earlier language was unclear to them.</p><p>Once in an expanded notification, users saw a short title indicating the most recent update, the live video, and 2–3 lines of copy with more details about the events pictured at the moment the alert was sent. As much of what was shown was planned or announced in advance, this copy included details about who was speaking and their titles, or some of the history of the ceremony.</p><p>In the expanded view, users could tap on the video to mute and unmute the sound, as well as tap on two action buttons, one of which took the user to the live blog, with the other offering the option to opt-out of the notification. If the user dismissed the alert by swiping it away, they received an immediate follow-up notification with a way for them to re-open the alert. We decided to send this follow-up notification based on feedback from previous experiments, when users who accidentally swiped away notifications were frustrated by needing to wait for another push to re-engage.</p><p>Over the course of the day we sent 29 updates to the live video notification, ending around 6:45pm EST, as the inaugural parade following the ceremony was coming to a close.</p><h4><strong>Numbers in Brief</strong></h4><p><strong>Audience Size:</strong> 620 users</p><p><strong>Engagement:</strong></p><ul><li>Users watched video for three minutes on average</li><li>Users expanded the alerts an average of between three and four times during the experiment</li><li>25% of users tapped through to the live blog during the experiment</li></ul><p><strong>From the survey:</strong></p><ul><li>Users who rated the alert positively, calling it useful, interesting and convenient: 85%</li><li>Users who said they would want this type of alert for Breaking News Events: 98%</li><li>Users who said they would sign up for this type of alert again: 89%</li></ul><h4><strong>What the Data Told Us</strong></h4><p><strong>Users on average expanded the alert multiple times.</strong> Users expanded the notification between 3 and 4 times throughout the day. 92.5% of survey takers also said they expanded the alerts they received, indicating that our instructions were clear.</p><p><strong>Users watched the live video in the notification for about the same amount of time that current wisdom suggests they watch video on the internet. </strong>The average play duration per user for live video was three minutes. That’s <a href="http://digitalnewsreport.org/publications/2016/future-online-news-video/">roughly on par</a> with some assessments of how long users will watch video in other digital news formats, and is in the upper reaches of expected attention time for an average video online today.</p><p><strong>Users came in at the important moments, and reengaged with the content that interested them. </strong>Reuters had published a schedule for subscribers of which events it would shoot on its inauguration feed, and then notified clients on the day of the inauguration that they would be cutting back and forth to the protests taking place that day in Washington DC. We adapted the text of the notification to make clear to users what the feed was showing when it switched to protests.</p><p>The switch to the protests proved to be the most popular update of the day, and the closest to a true “breaking news” event. 41% of subscribers expanded this alert to watch the video. Overall, users expanded between three and four times during the time we sent notifications.</p><p><strong>Users found the alerts convenient, useful and interesting, far more than they found them onerous.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*UuEo4I1AKoS801kp." /></figure><p>Survey takers indicated that they liked the convenience and utility that we were trying to put into the notification. From our subscription data we saw that the rate of users who turned off the notification over the course of the experiment was low, at 8% (while in the survey 80% told us they knew how to turn off the format if they had wanted to). Some who took the survey indicated that they had a hard time watching the video, or felt like it was more work, though, which gives us some indication that we could try to make the experience easier in future experiments.</p><p><strong>25% of subscribers tapped through the live blog over the course of the experiment. </strong>Users found the “Open live blog” button below the live video stream and tapped through to get more information, which suggests that even with direct access to the video, some users still wanted analysis, or preferred a written account of events.</p><h4>Additional Insights</h4><p><strong>Live video notifications, as well as being an industry first, held up well against our initial expectations and assumptions about their effectiveness as a means of conveying information.</strong> Most excitingly for us, 98%<strong> </strong>of users said that they would like this type of alert for a breaking news event. 89% said they would sign up for this type of alert again.</p><p><strong>Running this format on the day required a full time editorial staffer and developer. </strong>Developing this type of notification required dedicated work from Alastair, who created the format while working on the mobile lab’s iOS app. In addition, we consulted with the Guardian US video team in advance about the video streams they would be using, and how we might embed the video in a notification.</p><p>Editorially, we were able to create an editorial schedule with suggested copy in advance, with the official information available ahead of the inauguration ceremony. One lab staffer ran the titles and notification copy for the format for the day, watching the live video stream and sending updates through the tool. Another developer was dedicated to the format on the day, watching for breakages. We sent 29 push notification updates, including several breaking news notifications in the afternoon for which we wrote copy on the fly, between 11am and 6:45 pm EST.</p><p><strong>Live video notifications hold promise for live streamed breaking news. </strong>Our most engaged moment of the day was when we updated the alert as the live stream turned away from the official events of the inauguration to cover the protests in Washington DC. After the experiment, 98.3% of survey takers told us they would like these alerts for breaking news.</p><p>Additionally, of the 29 updates we sent that day, three others that had high engagement rates were those that signaled major events, like the arrival of the president-elect and the start of the ceremony. This suggests that this format can provide a handy way to prep users for news they know they would like to see, and then offer it immediately after.</p><p>We’re planning to try this format again and look forward to sharing it with you.</p><p>In the meantime, if you have questions or want to chat, send us an email at innovationlab@theguardian.com or find us on Twitter <a href="http://twitter.com/gdnmobilelab">@gdnmobilelab</a>.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532133e22419" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/live-now-from-your-lock-screen-532133e22419">Live: Now From Your Lock Screen</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[News that lets you do both: How we tested a read-and-watch live video feature]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/news-that-lets-you-do-both-how-we-tested-a-read-and-watch-live-video-feature-88271aa1126d?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/88271aa1126d</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[live-streaming]]></category>
            <category><![CDATA[breaking-news]]></category>
            <category><![CDATA[youtube]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Fri, 03 Mar 2017 19:25:56 GMT</pubDate>
            <atom:updated>2017-03-03T19:25:56.411Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>92% of users surveyed said they might want a mini live video player on a future live blog.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VX2ZmlwMcfES2SlaMBaz2g.jpeg" /><figcaption>Two birds, one… you get it. (Photo: Chris Grady/Alamy)</figcaption></figure><p>In one of our first posts, we wrote about what we thought were <a href="https://medium.com/the-guardian-mobile-innovation-lab/reimagining-the-live-blog-as-a-mobile-first-experience-e50d72f2197#.hntmpe8ch">missed opportunities for news organizations’ live blogs</a> in light of the growth of mobile usage. From implementing mobile-first behavioral paradigms, such as swiping and tapping, to creating the ability to find out what had happened earlier in an event without a prodigious amount of scrolling, we identified a number of possible ways to make live blogs, still the most common way news organizations present live coverage, more mobile-centric. In many instances we came to these possibilities in partnership with staff from <a href="http://www.codeandtheory.com/">Code &amp; Theory</a>, a design agency we worked with on a round of user testing and prototyping last year.</p><p>One of those ideas — the ability to simultaneously read live blog text and watch a live video feed — resonated well in usability tests, and so we decided to make this a feature to test live during the presidential inauguration on January 20.</p><h4>Why We Did It</h4><p>A number of news sites, including CNN and Bloomberg, already include this “read and watch” format — in which a small version of a video player appears at the bottom right of a screen of text. It is generally used for pre-recorded videos that are matched with an accompanying article, rather than a live video stream. The YouTube and Facebook apps also have a minimizing, pinnable video player, but the content in the video does not relate to that which the user is scrolling through.</p><p>In the read-and-watch scenario we prototyped to accompany a live blog, the text and video are likewise supporting the same event, and updating concurrently, but offering different information. The live video allows users to keep pace with events in the moment, while the text describes earlier moments.</p><p>For a live blog in particular, the ability to read and watch simultaneously makes sense for users who want to jump into the live blog and keep up with the current news, while seeing what came before.</p><h4>Our Hypothesis</h4><p>Our assumption in building this product was that <strong>giving users the ability to read text and watch video updates at the same time during a live news event would alleviate their need to choose between the two formats</strong>, which can provide complementary kinds of information. We thought that indicators of success would be the length of time people spent using the video player, as well as anecdotal responses in our follow-up survey that they found this format useful.</p><h4>What We Did</h4><p>On inauguration day, we made the read and watch format available on the Guardian’s live blog throughout the day, viewable on mobile web (as well as desktop) and in the Guardian iOS and Android apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*9VTxlCSfNSYXgrZlZsb9Og.png" /><figcaption>Live video player, pinned to bottom of inauguration live blog.</figcaption></figure><p>While the implementation scenario for the inauguration live blog differed from the uses of minimized video players by other news organizations, we kept much of the layout and features the same. When users entered the live blog, they saw the live video player pinned to the top of the page. After they interacted with the video — pressing or tapping to play — and then scrolled down the page, the video would minimize and be pinned to the bottom right corner of their screen, where it would stay as they scrolled further.</p><p>Even when the video was minimized, users could mute and unmute the video, play or pause the video or dismiss it by swiping it away or tapping a small ‘x’. They could also view the video in its original size by scrolling back to the top of the page.</p><p>Mobile lab developer <a href="https://medium.com/@cojennin">Connor Jennings</a> built this feature to be compatible with the YouTube player the Guardian has recently adopted.</p><h4><strong>Numbers in Brief</strong></h4><p><strong>Audience size:</strong></p><ul><li>200,000 users</li><li>57% of the 347,000 live blog readers who saw the feature used it</li></ul><p><strong>Cross-platform engagement:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*1eCud_Rx7u_8BB_a9MjwrQ.png" /></figure><p><strong>From our survey (linked to from the player):</strong></p><p>Users said:</p><ul><li>this format was easy to use: 85%</li><li>they liked being able to read and watch video at the same time: 85%</li><li>they might want it on all blogs: 92%</li></ul><h4>What That Data Told Us</h4><p><strong>Nearly 200,000 users interacted with the player on inauguration day.</strong> Inauguration Day live streams across all platforms broke all the Guardian’s records for live video, with the highest point of engagement just before Trump was sworn in.</p><p><strong>Over half of the users who saw the player engaged with it. </strong>The live video multitasking player was seen by 347,000 users on mobile and desktop, and used by 200,000, or 57% overall.</p><p><strong>Users had a high appetite for watching this video stream.</strong> The average play duration was just over 17 minutes! We did not track whether the video was playing in the primary tab, so we can’t tell if for some of the time the video was playing in the background. Still, the amount of time spent with the video playing suggests that live video is a content type that is of interest to users.</p><p><strong>Users appreciated choice in how to interact with the video</strong>.<strong> </strong>The average user tapped ‘play’ around 7 times and ‘pause’ half as often. These interactions formed the vast majority of engagement that users had with the video. In addition to ‘play’ and ‘pause,’ they had additional options to mute and unmute, and to dismiss the player by tapping an ‘x’ or swiping it away. Closing the video player or swiping away accounted for only 4% of interactions. On average, users muted and unmuted the video once. 85% of users surveyed also said was easy or easy enough to use the controls.</p><p><strong>The type and timing of engagement with the player varied by platform. </strong>Desktop users, who made up nearly 60% of the audience, also contributed the lowest number of average taps on the player, compared to mobile and tablet users. One possible reason for this might be each user’s location. Mobile users, who could be answering a text, opening another app, or even moving about their day, may instinctively be pressing pause, especially if they had the intention to return to the video. This also makes sense when you see that users on mobile had higher play actions than the more stationary desktop users — this could be their return to playing the video after pausing it.</p><p>Strength of the video stream may be another possible explanation (or culprit) if a user was moving around. It’s possible the video may not be loading as well —and it’s possible the higher tap actions are a reflection of a user trying to get a buffering video to restart or take time to load. Last, we saw a spike in desktop users pressing play when the first important guests arrived at the ceremony, however on mobile we saw a much steeper spike of users pressing play just a minute or two before the oath started. This suggests that desktop users started playing the video and browsed other tabs before checking back in on the stream during key moments, while mobile users, seemed more inclined to press play just before the key moments, and paused just after.</p><p><strong>Users told us they enjoyed and understood the experience — on both mobile and desktop.</strong> Generally in the mobile lab, we don’t focus on the desktop experience. But because the inauguration was a daytime, weekday event, and many live blog readers were working during that time, it was important to our team and others at The Guardian that this player function well on desktop as well. The survey we appended to the minimized player to ask for feedback was taken by 139 users, 65.5% said they had viewed the player on desktop, 19.4% on mobile web, and 15.1% in the Guardian apps. Of users who took this survey on all the platforms, 76% said was clear that the format was playing live video, and 12.9% said was somewhat clear.</p><h4><strong>Additional Insights</strong></h4><p><strong>Live video multitasking met our criteria for test success. </strong>To recap, we thought that indicators of success would be the length of time people spent using the video player, as well as anecdotal responses in our follow-up survey that they found this format useful.This first test reached a very large group of highly engaged users. And after interacting with the new feature, 92% of users told us they’d definitely or maybe like this feature to be available on all live blogs, a strong signal to move forward.</p><p><strong>Once set up, this video player could run itself. </strong>In planning for this feature we consulted with the video team about best ways to work with the Reuters stream. Additionally, we worked with the Guardian US interactives team and the Guardian web development team to adapt one of the interactive team’s existing modules to launch the player on the site. For those considering a similar feature, our experiment showed that people used this feature widely across platforms. Building this feature for this experiment then required the dedicated work of one developer, <a href="https://medium.com/@cojennin">Connor Jennings</a>.</p><p>On inauguration day, this feature did not require dedicated editorial staff to run. It did require some attention from the Guardian US video team, though. Occasionally, Reuters will change a live video stream in the middle of an event. Had that happened we would have needed to locate and embed the new stream. Thankfully, that didn’t happen during the inauguration. We’re grateful to Guardian news video producers Clare Downey and Chris Whitford for keeping tabs on the stream that day on top of their other work.</p><p><strong>The video player was a way to test the very idea of multitasking on a single screen on mobile.</strong> Our audience for this experiment had the largest percentage of desktop users, but still provided some interesting takeaways in terms of what we expect users to be able to do on a mobile screen versus desktop.</p><p>Relatively new features like Facebook Live and the YouTube app have introduced users to the idea of multitasking on mobile, where they might expect to scroll and watch at the same time. Neither were built with the consideration that you might want to watch the live video from an event while <em>also </em>reading about it. Contrast this to desktop, where autoplaying ads, similar video players and other features, even tabs, assume that multitasking is the default behavior. Do users want to multitask in the same way on mobile? The feature needs further testing, but our initial sense is that the answer is yes.</p><p><strong>Expect to see the most interaction when the main event is happening. </strong>In this case, we consider the main event to be the moment the oath of office was being taken, just around noon. We saw the greatest number of users hit play minutes before then, and sharply decline afterward. We did not see a resurgence of activity (and even then a comparatively modest one) until the breaking news of protests later in the afternoon.</p><p><strong>Future plans: Refine the controls and possibly give users greater control over size and location of the player. </strong>Users seemed very enthusiastic about this live video feature but had some specific suggestions about how they would like to interact with it. In the survey, users particularly asked for the ability to control the size and placement of the player. Some also mentioned some “jumpiness” upon scrolling, which should be smoothed out for a better experience. From a tracking perspective, it would be helpful to know if the page with the player is sitting in a background browser window, rather than being actively watched.</p><p>Did you see our mini live video player? What did you think? What would you like to see next time? Send us a note to <a href="/service/mailto:innovationlab@theguardian.com">innovationlab@theguardian.com</a>.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88271aa1126d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/news-that-lets-you-do-both-how-we-tested-a-read-and-watch-live-video-feature-88271aa1126d">News that lets you do both: How we tested a read-and-watch live video feature</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shifting Lenses: A first look what a mobile-centric live blog could be]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/shifting-lenses-a-first-look-what-a-mobile-centric-live-blog-could-be-7eae9a3a634b?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eae9a3a634b</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[liveblogging-history]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Fri, 20 Jan 2017 14:25:24 GMT</pubDate>
            <atom:updated>2017-01-27T15:48:10.144Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZTrTndZgRN7BmzyY_XmUw.jpeg" /></figure><p>As part of our i<a href="https://www.theguardian.com/world/2017/jan/18/inauguration-day-mobile-lab-experimental-features">nauguration experimentation</a>, we have a new feature we’d like you to try. We’ve taken the basic elements of a live blog and reworked them to create what we hope will be the first step towards a better experience of live coverage for a mobile readership.</p><p>Some background: Last year, at the start of the lab, <a href="https://medium.com/the-guardian-mobile-innovation-lab/five-proposed-areas-of-focus-for-mobile-innovation-in-news-1545f8da2528#.hsjd2m1ah">we started thinking</a> about how live coverage could better suit a mobile-first era, and noticed how little had changed since live blogs became a popular format used by a large number of news organizations, in a pre-smartphone era. We looked at lot of live blogs covering a variety of news events and noticed they shared a number of <a href="https://medium.com/the-guardian-mobile-innovation-lab/reimagining-the-live-blog-as-a-mobile-first-experience-e50d72f2197#.qds6zw89a">common features</a>, ones that make them ill-suited to modern mobile reading habits.</p><p>First, there’s currently really only one way to move through most live blogs — from the most recent update to the oldest. This organizational principle matters when you consider all the different times readers may be entering a live blog. There are very few clues as to what has happened prior to the first update they see (usually the most recent) and what the latest post means in the context of others. That most recent post might build on a narrative thread the blog has been following for some time, or introduce a new topic, or correct an earlier assumption.The reader is left to decipher for themselves how it fits into the whole..</p><p>Second, and most relevant to this experiment, a live blog doesn’t consider that a user might find some information in the live blog more interesting or more useful than other pieces of information. For example, some users may prefer maps or other visual elements to text describing a location. These limitations are compounded on mobile where reading a live blog can feel like an exercise in endless scrolling.</p><p>On the conviction that there has to be a better way to make reading a live blog a more enjoyable experience on mobile, we worked last year with the agency Code &amp; Theory to design and test a variety of experimental features that would avoid some of these common usability pitfalls.</p><p>User testing on the prototypes we developed with Code &amp; Theory validated some our ideas about how users might like to experience live coverage differently on mobile if given the opportunity. Participants in user testing, all of whom habitually read news on mobile, told us they liked having additional views that presented live coverage in separate chunks of information. They also liked the idea of having better navigation within a live blog and that, while they liked the overall feel and timing of a live blog, they liked the idea of having views that could provide additional visual context and location easily.</p><p>With these insights in mind, we took one of the features we (and our testers) were most interested in, and have built it to test out for the first time as a proof of concept on inauguration day.</p><h3>The feature is called Shifting Lenses, and it’s designed around the idea that multiple views on a story help users to better follow live coverage.</h3><p>We’ve adapted the original prototype for the inauguration, and introduced “lenses” called On the Podium and Off the Podium, which will follow, respectively, everything happening on stage and in the official program, and everything happening off the podium and around those events. Both narrative lines will be critical to making sense of the day’s events, and we hope presenting them this way will keep some of the nuanced moments of the day from getting lost.</p><p>For this first test, all of the content for the lenses will come from the Guardian live blog. We are running a <a href="https://www.theguardian.com/world/2017/jan/18/inauguration-day-mobile-lab-experimental-features">number of other live features</a> on inauguration day, so this feature will begin in the afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*FFEqPKBY4-9_1INH7gDPdQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*X27tMQoS7jNC-DUaROGuzA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*MCwANCKqxLa8NdeRqNAZjA.jpeg" /><figcaption>Three views of the inauguration day Shifting Lenses Left. On the Podium, Center: all posts in a combined view, Right: Off the Podium</figcaption></figure><p>From this first test, we’re looking to validate (or disprove) some of our initial hypotheses, and get baseline data on how users interact with this feature when it is applied to a real event. Specifically we’ll be looking to see if and how often users swipe between the views, and what they tell us about how this new feature affected the way they consumed the news.</p><p>We hope you’ll try it out, <a href="https://www.theguardian.com/world/2017/jan/18/inauguration-day-mobile-lab-experimental-features">along with the other experiments we’ll be running that day</a> and let us know what you think.</p><p><strong>To do that:</strong> <a href="https://itunes.apple.com/us/app/guardian-mobile-innovation/id1194055480?mt=8">Download the Guardian Mobile Innovation Lab iOS app</a> and tap sign up to subscribe to notifications. You’ll receive a notification when we begin the experiment leading you to Shifting Lenses. Or, <a href="https://app.gdnmobilelab.com/inauguration/">click here</a> for a web view.</p><p>After the experiment concludes we will send a survey asking for feedback. Let us know what you think then, but if you have questions in the meantime, send us an email at <a href="/service/mailto:innovationlab@theguardian.com">innovationlab@theguardian.com</a></p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eae9a3a634b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/shifting-lenses-a-first-look-what-a-mobile-centric-live-blog-could-be-7eae9a3a634b">Shifting Lenses: A first look what a mobile-centric live blog could be</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four key takeaways from our election night live notifications experiment]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/four-key-takeaways-from-our-election-night-live-notifications-experiment-7a148ade899c?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a148ade899c</guid>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[2016-election]]></category>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Fri, 30 Dec 2016 18:14:17 GMT</pubDate>
            <atom:updated>2017-01-03T23:19:17.312Z</atom:updated>
            <content:encoded><![CDATA[<h4>Start early, recruit clearly, get everyone in a room, and stress test</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wRIHc9LikFD6ZrI6uXWSaw.jpeg" /><figcaption>Photo by Mikael Buck</figcaption></figure><p>After <a href="https://medium.com/the-guardian-mobile-innovation-lab/building-the-guardians-live-elections-notifications-87bafbcf510#.xiygktqvp">writing up how we planned, designed, and helped build</a> the Guardian’s live updating notification for the US presidential election with the UK apps team, we thought there was still space to define some takeaways for publishers looking to try live data-driven notifications.</p><p>Election night was our first attempt to launch this (or any) new notification format for iOS users, and it was the first time that an experimental format we validated through smaller tests was integrated into the Guardian apps.</p><p>Some of the takeaways are specific to our process, but we hope what we’ve pulled out here will be helpful to anyone looking to try a similar format.</p><h3><strong><em>1. Live-updating alerts make sense to readers and drive app traffic.</em></strong></h3><p><strong>Live updating alerts provide value at a glance.</strong> The Friday following the election we sent a survey to our notification subscribers asking for feedback on the experience. About 83% of the more than 6,000+ users who responded told us that the alert clearly and effectively communicated the important results in one place, letting them know what the news was, at that moment.</p><p><strong>The live-updating alert format was easy to use and understand. </strong>The majority of users expanded the alerts, proving that it was easy to do so. Even more told us that they understood how the live-updating alert worked, even though a persistent alert that replaced itself with new data was an entirely new format for our audience.</p><p><strong>The live-updating alert generated significant app traffic during the event</strong>. These alerts reached an audience of more than 230,000 Guardian app users, and drove 800,000 page views to the Guardian’s election night live blog and pages containing a full breakdown of results. Traffic from the alert accounted for about 6% of overall page views to the live blog on election night. A majority of alert subscribers (74%) contributed to that traffic by engaging with the alerts — tapping through on the alert to open the Guardian app.</p><h3><strong>2. In-app sign up is a successful recruiting tool for new formats, but the call out and description needs to be very clear and simple.</strong></h3><p><strong>Sign-up should be easy and options should be tailored to your anticipated audience’s interests. </strong>The language and graphics on our sign-up page were clear, quick and simple, and we customized the opt-in/opt-out function based on a user’s location. Specifically, where possible, we chose to default US users to being opted in to the alert, with the option to opt-out; for users outside the US we defaulted them to being opted out, with the option to opt-in. We decided to differentiate the default behavior based on location since we thought users in other countries might be less interested in live US election results than those in the US.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*p1go9VfUjXFpTfni0nrUwQ.png" /><figcaption>Sign-up screen for US app users</figcaption></figure><p><strong>As much as possible, explain exactly what you are offering at the point of sign-up.</strong> More on that call to action: We went back and forth amongst ourselves and with other editors in the Guardian US newsroom about what the sign-up screen should say and how to describe this brand new format. Were they auto-updating alerts? Live alerts? What would pique a user’s interest, but also help them understand the offering? In the final wording we attempted to strike a balance.</p><p>Happily the attention to detail paid off: 62% told us in survey feedback that it was clear the alert would update, with an additional 23% reporting it was somewhat clear.</p><p><strong>Since a notification is small, first determine the hierarchy of information that should appear, and be disciplined about the character limit. </strong>We recommend forming a multidisciplinary team early on, including representatives from editorial, product, development and design, to determine the key pieces of information you’re trying to deliver, and how to best display them in the alert. Tackle questions like: If someone doesn’t expand the notification, what is the most important information for them to still see? In the expanded view, will all the information fit on a smaller phone screen? Asking these and other questions will help you ensure that a majority of your users have a great, and complete, experience with the alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*x5QQ9fosQetleVwd2rjQLA.png" /><figcaption>Collapsed versions of the alert on Android (top) and iOS (bottom)</figcaption></figure><h3><strong>3. Successful collaboration on new formats requires extra planning, communication, and possibly, new tools.</strong></h3><p><strong>Start planning work well in advance, and seek out newsroom input on every piece of the experiment, from sign-up page to follow-up survey.</strong> While many newsrooms are starting to collaborate more often with product teams, developers and design groups within their organizations, the process still isn’t seamless. For example, in this project, we worked out nearly all of the details for in-app sign-ups directly with the UK apps team, without first realizing that the newsroom would want to weigh in on that copy, the visuals and how the alert was offered to app users. Because we didn’t consider the sign-up strategy as one of the editorial considerations for the alert, we weren’t as inclusive as we should have been with that decision making. This meant that, just days before the alert launched, we had to either jam in or completely roadblock a few small but significant changes to the sign-up process.</p><p><strong>When experimenting with apps, discuss development deadlines up front.</strong> For many newsrooms, changes to web features can be made just before or even during a live event. When building or integrating with a native app however, teams need more lead time to make changes, since making changes to apps sets off a much bigger chain of events. With apps, changes must be coded, tested on multiple devices, submitted to an app store, approved and then made available to users for download.</p><p>It would have been wise of us to discuss the differences between web and app development with stakeholders in advance, so it was clearer why changes could and couldn’t be made in the days leading up to the election. It also would have helped to signal that the app approval processes differ between iOS and Android, and that most elements of the alert needed to be hard coded into the apps well in advance before they could be submitted to the App Store or Google Play.</p><p>For this alert, the sign-up screen and the integration of the AP data feed needed to be finalized before the app updates could be submitted for Google and Apple’s deadlines, facts that we didn’t make clear enough to the editors working with us on the project. The upshot: make sure to kick off the collaboration by identifying all of the decisions that will need to be made, by whom, and by when.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*zdqzv48Zyu8nqd-ODNKNvw.png" /><figcaption>Scrutineer, the tool <a href="https://twitter.com/mrdrjennings">Connor Jennings</a> built to manually control the alerts</figcaption></figure><p><strong>Consider building an editorial tool that helps facilitate the creation of content, and also a deeper understanding of the format.</strong> The content management tool we built for this alert allowed our team, and in theory the news editors we work with, to independently edit the alert title, body copy and graphics, and was created with simplicity and flexibility in mind. When working with a new format, having a tool with an easy-to-use interface can help all involved visualize the output.</p><p><strong>App notifications need time to be tested on phones of varying screen sizes and operating system versions, in order to find and fix issues. </strong>Staying within the character limit in a notification is a continual challenge, as is determining the number of lines you can display in a notification before some information gets cut off. Make sure to test your content on a wide variety of screens and across platforms to make sure the most important information always appears. We made some last-minute adjustments when we realized that phones with a slightly larger than factory-set font size would cutting off the popular vote percentage. We shortened “Popular” to “Pop.” and managed to restore the full content on those phones, but looking at a device with those settings in advance would have helped.</p><h3><strong>4. In order to ensure a positive user experience, great visual and experience design are just as critical as quality content, and require as much precision and flexibility as other elements of coverage.</strong></h3><p><strong>If you want to use a graphic in a notification, ask yourself first: “What additional useful information does it convey?” </strong>Notifications have limited space, so anything you decide to include needs to have a clear purpose. We decided to include a data visualization of the great 8-bit candidate avatars, designed by the Guardian US Interactives team, on top of a bar chart showing the number of electoral votes each candidate won relative to the 270 vote threshold.</p><p>We included the graphic not only because it was eye catching, but also because it was a more visual way to represent the electoral vote data, especially the ratio being apportioned in real time. If you decide a visualization is an important element of your notification, make sure to label what it is and what it represents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/325/1*BdMWi_1S843R7qKCaZJZmQ.png" /><figcaption>Three action buttons: Open Live blog, Full Results and Opt Out</figcaption></figure><p><strong>Action buttons should only offer the most important and interesting functionalities.</strong> Since interacting with a notification beyond just tapping on it to go to an article is a very new concept, it’s important to make sure that the interactions you make available in the action buttons are clearly labeled and are useful or interesting. Again, just like with the content within the notification, you want to talk with your team about the hierarchy of the interactions, and show them in order of importance.</p><p>Because one of our goals was to gauge the audience’s appetite for information beyond that contained in the notification, the first two action buttons gave access to the live election night blog and also the full election results pages. The third button was a mechanism to opt-out of the alert, which was important to surface and make easy for the user to do, but was less important than giving easy access to more content. The action buttons are a powerful way to add value to a notification, so make sure you appropriately dedicate them to functions that help you learn about what your audience wants from new alert formats.</p><p><strong>Notifications are usually subscribed to and sent through a service outside your CMS, so stress test that service in advance, especially for a spike in alert subscriptions. </strong>On election night some people who signed up for the alert indeed never received it because our push service was overloaded with subscription requests and couldn’t register them all. We recommend stress testing the push service in advance. Additionally we will be looking at ways to send a message to users confirming that they are signed up.</p><p>As always, if you have thoughts or questions about the alert, or even how we’ve structured these takeaways, reach out to us here in the comments, on <a href="https://twitter.com/GdnMobileLab">Twitter</a>, or by e-mail at innovationlab@theguardian.com.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a148ade899c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/four-key-takeaways-from-our-election-night-live-notifications-experiment-7a148ade899c">Four key takeaways from our election night live notifications experiment</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Profiles in Notifications: Lessons Learned From the Jobs Report, Round 6]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/profiles-in-notifications-lessons-learned-from-the-jobs-report-round-6-bf055c64df66?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf055c64df66</guid>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[economy]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[journalism]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Wed, 28 Dec 2016 21:57:13 GMT</pubDate>
            <atom:updated>2017-01-04T19:59:45.603Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sending snapshots and receiving responses</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uaXWJTbncBeCyz0m-02IBQ.jpeg" /><figcaption>Photo by Rex Features</figcaption></figure><p>October marked the sixth time we’ve covered the jobs report through notifications. To recap, up to that point we’d done four rounds of experimentation with interactive notifications and one month of a reader call-out through notification. For October’s jobs report we decided to change the format again.</p><p>We again worked with Jana Kasperkevic, a business reporter, and her editor, Dominic Rushe, to come up with a plan. Several months earlier Jana had mentioned that September 2016 would be the eight-year anniversary of the US economic crash — an entire presidency ago. Jana was working on a set of profiles of Americans, asking them how they felt they had fared over the last eight years. At her suggestion, we decided to adapt that piece into the October experiment.</p><p>Jana’s story, “<a href="https://www.theguardian.com/business/ng-interactive/2016/oct/08/great-recession-financial-crisis-recovery">The Great Recession, the hollow recovery</a>” was published the day after the jobs report went out and included interactive elements and a custom format. The piece included excerpts of text and audio from interviews Jana conducted with five Americans whose lives had changed since the beginning of the recession. When combined, these excerpts gave a very human perspective on a story that otherwise has been mostly about the numbers.</p><p>In adapting the profiles, we also tried to include some of that perspective in the notifications.</p><h4>The Notifications</h4><p>This experiment differed from earlier jobs report experiments in a few ways. We tested a new format, as well as new timing.</p><p>First, because Jana’s piece came out on the Saturday after the jobs report was released, we needed to alert our jobs report subscribers that we were going to be changing the timing of our experimental alerts, which we had been sending to coincide with the release of the numbers early in the morning of the first Friday of each month.</p><p>We sent our first notification on Thursday afternoon, and told our jobs report audience that we would not be sending our experimental jobs report notifications at the normal time on Friday morning but to look for us on Monday.</p><p>Then on Monday around 2pm ET, as promised, we sent a series of sequential notifications, each linking to a specific profile within Jana’s article.</p><p>We called these notifications snapshots, because each of the five contained a short quote from one of the people interviewed in Jana’s piece, and included their photo as the notification icon. The title of each notification included their name and age.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*ldCsBj3MxSZul0uY." /></figure><p>The action buttons in each snapshot offered users the option to go to the full story, which, with the assistance of the Guardian US interactive team, deep-linked to the area of the story that had that person’s profile. The snapshots were also persistent, meaning that even if you tapped on the notification itself, rather than the buttons, the notification stayed in place until you dismissed it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*0EWpv1tYuA0V_Gt9." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/0*mtKVo9D7nL5Asn8T." /></figure><p>We followed up these snapshot alerts with a final notification, sent at 5pm ET on Monday, with a call-out to users inviting them to tell us their stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*aReemYxyuuZXdXH-." /></figure><p>This built upon the call out from the <a href="https://medium.com/the-guardian-mobile-innovation-lab/crowdsourcing-through-notifications-lessons-learned-from-the-jobs-report-round-5-c255b876badb#.t3wj9arll">previous month</a>, when we had first tried a call-out through notificationsm which hadn’t elicited any replies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/323/0*Eq0cZpHzNEqniD51." /></figure><p>In response, and to further explore whether notifications can be effectively used for crowdsourcing, we made a few changes to call-out format for this month.</p><ul><li>First, we asked users a specific question, and made clear that their answers might be used in a future story.</li><li>We also sent the alert much later in the day. The previous month’s alert went out at 9am ET on a Friday, where this alert went out at 5pm ET on a Monday.</li><li>We also changed the method through which users submitted responses. While in the earlier call-out users responded through a Google form, this time we lead them to a submission page on The Guardian US site, which had the added benefit that we were able to more prominently display our branding.</li></ul><p>Last, on Tuesday, we sent a notification with a survey asking for feedback on the experiment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/357/1*13K_OTlpqyU7TlW0ZerCVA.png" /></figure><h4>How They Worked</h4><p>With the different types of notifications sent, there are a few interesting metrics to consider for this month’s experiment:</p><p>We sent the snapshot notifications to 303 subscribers and registered that they were shown to 49% of users. 63% of users closed the first notification, and 25% tapped on the first notification itself to open the article.</p><p>In addition, 8% of users tapped on the action button of the first notification to begin the snapshot sequence. Of that 8%, 75% made it all the way through the five notifications, and 42% then clicked through to Jana’s full interactive.</p><p>Our call-out notification was shown to 52% of subscribers, of which 47% closed the notification and 17% tapped on the notification itself, which brought them to the submission page. An additional 6% tapped on the “Tell Us” action button, which had the same effect.</p><p>In an exciting development, we received nine responses to our call-out through the submission page, which was really encouraging after the lack of responses the previous month. These users told us how the last eight years had affected them, and who they would be voting for for President — both remarkably personal things to share — and told us we could contact them.</p><p>We believe this demonstrates that they both understood and enjoyed the experience enough to want to share, and that call-outs through a notification, when properly framed, can be an effective way to ask audiences for participation.</p><h4>What We Learned</h4><p>As always, the survey was a valuable tool for gauging the effectiveness of the experiment. Our 21 survey respondents told us more about how the call-outs and profile-driven notifications worked, and continued to shed light on our jobs report audience, who we’d been experimenting alongside for six months.</p><p><strong>The snapshot notifications conveyed a more personal experience. </strong>It was the quotes, our survey respondents told us, that made the notifications feel more personal, and to a lesser extent the head shots as well, rather than the prompt we used to move through the notification, “Meet ______”, or our call for their personal stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/0*wCQqK6tCU3GemiZG." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/0*Z_tKc4XwfqeIM_rX." /></figure><p>This type of format might also be a way to connect readers with a topic they don’t have a particular affinity for — by using personal narrative. One user wrote in to tell us that they thought you didn’t need to be interested in economic news to be interested in these notifications.</p><p><strong>Timing, or some still unknown element, still dictates when users choose to interact. </strong>As we continue to explore this topic with a dedicated user base, we’ve also started to ask questions about the users themselves, and that get to what makes them engage. This time, we asked users, “If you didn’t tap through, why not?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/0*2r3WYg01sWtLij_N." /></figure><p>Some users told us they didn’t receive the alert, which we know to be an ongoing problem. Others said they just weren’t interested. However, 27% said that it was because they received the notifications at an inconvenient time. We sent the snapshots at 2pm ET on a Monday, hoping to hit a midday audience looking for a break, after seeing very little engagement on sending in the early morning the previous month.</p><p>This month’s 8% tap-through rate is slightly lower than the 10% we saw in for both the September jobs report experiment (for which we also sent sequential notifications) and the August experiment. In September, we also sent the alerts later in the day, while in August we sent alerts at 10am ET on a Friday.</p><p>An interesting observation is that none of our users chose “The icon threw me off” as a reason they didn’t tap through. For this month’s experiment, our icons were a penny, and then head shots of the interviewees from the article. None of our icons had Guardian Mobile Lab branding, yet, this didn’t seem to confuse the audience.</p><p>While we could have been more specific in the way we worded the response (current wording doesn’t allow for the possibility that a user doesn’t know what an icon is), it’s rare that zero people select one of our multiple choice answers, so it’s worth theorizing why that might be.</p><p>For this experiment, we delivered non-Guardian icons because we were trying to challenge the notion that an alert icon needed to be used for news source branding or attribution. We wanted to explore the possibility of using that space (since space is so limited in an alert) to convey different signals or supplement alert content.</p><p>Based on the survey response, there are a few possible interpretations. First, as mentioned above, it’s possible users didn’t know what the term “icon” meant. Second, it’s also possible that users don’t pay as much attention to alert icons as we think they do, or third, users understood that the alert was coming from the mobile lab without needing it to have a branded icon. With further testing, we’ll hope to be able to confirm whether or not publishers can start reclaiming the icon space for something other than branding.</p><p><strong>Users either appreciated or didn’t notice that the notification was persistent. </strong>Implementing the persistent notification (it didn’t disappear when it was tapped on) was a good on-the-fly suggestion from Connor Jennings, one of the lab’s developers, and the majority of users either didn’t mind it or found it convenient. Because each individual notification was unique and deep linked to the relevant area of the interactive, this also meant the user could use this additional navigation at their convenience rather than having to choose which notification to tap through on and losing the rest of the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*5NBwPtai5SqUYgVx." /></figure><p><strong>Users weren’t sure what to think of the call-out. </strong>The survey responses to the call-out were a bit of a mixed bag. While 29% of users said they liked it, the same number said they weren’t sure about it, and the rest either didn’t like it or weren’t sure what we wanted from them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*3DCqIei8XqwJ0Dwk." /></figure><p>So despite the responses we did get, we think there is an inherent challenge to making call-outs through notification effective, because of the lack of in-line replies, which are are not currently available through web notifications.</p><p>While we were excited about the increase in replies this month, there’s still clearly more to learn there both in terms of signaling what we are looking for, and how we are asking for it. In-line replies are <a href="https://groups.google.com/a/chromium.org/forum/#!topic/Blink-dev/9s8Zamqbv34">still a ways off</a> for web notifications — they’re an area we think is worth exploring but the technology needs to develop further before it becomes a seamless experience.</p><p><strong>We’re starting get a sense of a good sequence length. </strong>This month we sent nine notifications, including the notice that the experiment would be different, the six-part sequence, the call-out, and the survey. While the engagement with the snapshots was slightly lower than that for sequential notifications in our previous series, the vast majority went all the way through, and drop offs were at the beginning of the series rather than atrophying toward the end. In addition, engagement with the call-out, which came later, was much higher than it had been for previous call-outs. Finally, survey respondents overwhelmingly told us the notification number was appropriate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/0*fK91iNym3XxzfEwA." /></figure><p>We’re taking a break from jobs report experiments for now while we focus on experimenting in other areas.</p><p>We always enjoy hearing from readers and those experimenting in the mobile space. Let us know if you have additional ideas and observations in the comments or email us: innovationlab@theguardian.com. We look forward to hearing your thoughts.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf055c64df66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/profiles-in-notifications-lessons-learned-from-the-jobs-report-round-6-bf055c64df66">Profiles in Notifications: Lessons Learned From the Jobs Report, Round 6</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building the Guardian’s Live Elections Notifications]]></title>
            <link>https://medium.com/the-guardian-mobile-innovation-lab/building-the-guardians-live-elections-notifications-87bafbcf510?source=rss-2be18f4905fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/87bafbcf510</guid>
            <category><![CDATA[alerts]]></category>
            <category><![CDATA[web-notifications]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[2016-election]]></category>
            <category><![CDATA[journalism]]></category>
            <dc:creator><![CDATA[Madeline Welsh]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 21:38:13 GMT</pubDate>
            <atom:updated>2016-11-28T19:46:33.265Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we put real-time updating AP results data straight on the lock screen</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sk0CPAX4t6guyDT7lq34sA.jpeg" /><figcaption>Photo by Xinhua / Barcroft Images</figcaption></figure><p>Well. That happened.</p><p>November 8th was a big day. Big in a lot of ways we won’t get into here, but it was unquestionably consequential. For the Mobile Innovation Lab, election night was big in not-so-obvious ways: we, along with the Guardian’s US news desk and interactives team in New York, and the apps product and development teams based in London, broke new ground with news notifications by offering a live updating alert of election results as part of the Guardian’s election coverage.</p><p>Working alongside the excellent Guardian teams, we used a modified AP data feed to show up-to-the-moment elections results in a single alert that automatically updated with the latest results throughout election night. We offered these worldwide to users of the Guardian iOS and Android apps, and offered a quick sign-up experience to US-based users on both platforms.</p><p>This was, to our knowledge, the first use of the new iOS 10 notifications technology in this way, and absolutely the first time live notifications that auto-update have been used on a US election night. It was also the first time the lab’s work was available on iOS, and the first time work we had done was integrated into our parent organization’s main coverage and core products.</p><p>From the outset of the lab, we knew we wanted to experiment with a variety of ways we might tell stories or pieces of them through notifications, and to see what would resonate with audiences. We also wanted to experiment on the two biggest mobile platforms, Android and iOS. After much experimentation on Android through web notifications, and once more of the specifics of iOS 10 were announced last summer, the plan to create live updating notifications for both platforms became more of a reality.</p><p>The elections alert was in many ways the scaled-up version of the the experiments we ran during Brexit and the US Primaries. While we were only able to serve a relatively small audience on Android during those projects, the lessons we learned from them greatly informed the plans for and scope of the election night notifications. In particular, we adapted lessons learned in how to present and order different data points, how to signal that there was new information, and how to allow users to opt out.</p><p>While these notifications were an extension of the lab’s earlier experiments and allowed us to test many of the same assumptions with a much larger audience, they were also a part of the Guardian US’s overall package of coverage on election night, which also included a live blog, a detailed map of results built by the interactives team (also built around AP data and which offered detail down to the county level) and the more traditional text-based alerts sent to Guardian app users at key moments.</p><p>Because the results alerts were integrated into the apps, we were able to attract a far bigger audience than we have had in earlier experiments, which allowed us to learn far more about how the alerts were used and how well the format served the readers who received them.</p><p>Below is more detail on what we did and what it amounted to:</p><h4><strong>Presenting a hierarchy of information for users across platform and screen size:</strong></h4><p>When planning these notifications, we started by figuring out what information was the most important to be displayed without any user interaction required in the collapsed view of the alerts.</p><p>We also needed to think across platforms. iOS and Android alerts show different amounts of information in their collapsed states. On iOS we were able to get a bit more information in without having to expand the alert, whereas on Android, we needed to make some tough choices on what information took precedence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*JTB6tz4jEwFk3L-WZytqow.png" /><figcaption>The collapsed view of the alerts as they appeared on Android (top) and iOS (bottom)</figcaption></figure><p>We first sent the alert with a title — e.g. LIVE NOW: US election results — that would give a clear signal that the results were now coming in. Both alerts featured the Guardian logo, but with the news desk also sending update alerts with the same logo, we wanted to to differentiate between them by indicating that this was a live results alert. We did that in the title, which on each platform had a version of the words live election results.</p><p>Second, because the electoral vote is ultimately what matters most in determining a winner (deep breath), it was the next piece of information that was critical to appear on the collapsed version of the alert on the user’s lock screen. We provided a rolling count of electoral votes as they were reported by the AP.</p><p>On Android, that’s all we were able to show in the collapsed alert. On iOS we were able to display two additional bullet points to give more context about the electoral vote: reminding users what number of electoral votes we were counting towards, and indicating how many states had been called.</p><p>In the expanded view of the notification, which you get to by pulling down on the notification on Android or hard pressing on iOS, we were better able to achieve parity of information across platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*mLld4lzvLhH-egTJ4MaX_Q.png" /><figcaption>The expanded view on Android</figcaption></figure><p>Each of the expanded notifications included a data visualization of the electoral votes and the amount needed to reach the winning threshold, accompanied by the delightful 8-bit illustrations of the candidates, created by the Guardian US interactives team.</p><p>In the expanded view we were able to show four bullet points of information on each platform. (If we had been less worried about parity between platforms, we could have had more on iOS). In the four lines we were able to have on both, we looked to present several pieces of information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/329/1*F8vztuWkgqliO4bV2XE2TA.png" /><figcaption>The expanded view on iOS</figcaption></figure><ul><li>Number of states called: This provided context of how much more was to come in the electoral count, as well as the popular vote.</li><li>Number of swing states called: We thought indicating how many of these states’ results had been called might give an idea of the direction of the electoral count. We also displayed the abbreviation of as many of these states as possible. We were able to fit in up to three abbreviations, or two and “incl.” per line.</li><li>Number of precincts reporting: Similar to the number of states called, this number was intended to give context and indicate the progress of the popular vote.</li><li>Popular vote percentage: Again, we thought that the percentage of all votes that each candidate had won, according to the precincts reported, would provide a sense of how Americans were voting.</li></ul><p>We chose these categories based on our own knowledge of US election coverage, talks with others in the newsroom about what they would be reporting, and what information we received from the AP.</p><p>In addition to determining how the data would display in the notification, we also took two important user experience features into account, and built controls for them into the tool used to customize the alert.</p><ul><li>Major news updates: Through a tool built by Connor Jennings, one of the lab’s developers, we had the ability to change the alert title (and also to interrupt the bullet points, though we never used that feature). As major states and swing states were called, we changed the title of the notification to show the most recent and important news.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*6hBOBoZ8Ut8QaHwLOwuj_w.png" /><figcaption>Screenshot of the notification editing tool Connor built for election night</figcaption></figure><ul><li>Notification noise: There’s rarely a use case for a news organization to send a silent alert given the way that push notifications are usually used for breaking news. But for an updating notification, taking advantage of what has been a latent opportunity on Android and iOS (the ability to send a silent notification) suddenly made a lot more sense. We decided to have our initial notification to make sound, but all updates thereafter would be made silently. If the election had been called by midnight ET or so, we intended to have the alert buzz and make noise as the electoral count reached 270. Such as it was, the race was called at just around 3AM ET, and we opted not to.</li></ul><p><strong>Finding our audience:</strong></p><p>Part of what we discussed and worked with the UK apps and product teams on was how to opt users into the alert. Typically in our experiments we get people to sign up by pointing them to web page. Since the feature was built into the Guardian apps this time we relied on an onboarding screen — a recruitment tool the UK teams had successfully implemented in the apps for two earlier alert-driven features in the apps, the <a href="https://www.theguardian.com/us-news/series/the-campaign-minute-2016">Campaign Minute</a> and the <a href="https://www.theguardian.com/football/live/2016/jul/02/the-euro-2016-minute-blydi-hell">Euro 2016 Minute</a>. The onboarding screen was a full-screen message to app users explaining what the alert was, and how to sign up or opt out. For election alerts, users saw the screen the second time they opened the latest version of the Guardian’s iOS or Android app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/313/1*fE48KMK6yYKqqzJnt0DuFg.png" /><figcaption>The onboarding screen, as it appeared to iOS users</figcaption></figure><p>This screen gave a short description of the alert and let the user toggle on or off the alerts. The onboarding screen ran on iOS and Android in the US, and on Android in the rest of the world. In the US, we had the toggle set to opt users in, in recognition that they were geographically more predisposed to be interested in the results than those using the Guardian app internationally. We reflected that assumption by having the toggle set to off in the onboarding screen users saw outside the US.</p><h4><strong>How they did:</strong></h4><p>More than 230,000 Guardian app users subscribed to our alerts. For earlier experiments, our largest audience had been about 14,000 (for our Brexit web notifications). The increase, though largely due to the integration into the Guardian’s core apps, was a huge coup for the mobile lab. Thank you to everyone who tried it out.</p><p>In addition to those who already had the app installed and saw the onboarding screen, the UK apps team registered 20K to 25K additional Android app downloads during recruitment time.</p><p>Our users were located across the globe, with the greatest number of engaged users in the US, followed by the UK, with Australia, Germany and Canada occupying the third through fifth spots respectively.</p><p>The differences in global sign-ups were clearly reflected in the platform split we saw. Overall we had 170,000 Android subscribers worldwide. The onboarding screen was served worldwide on Android, providing a one-tap solution for users. By contrast, the onboarding screen was only served on iOS within the United States and we saw fewer worldwide subscribers as a result — 60,000 users opted in.</p><p>While we’ve worked to build a comprehensive experience within the notifications themselves, we are also interested in learning more about how users tap through on the alerts, and how they use the additional functionalities we programmed into the action buttons. Overall, we were really pleased to see the amount of traffic the notifications sent into the app, and the degree to which users used the new button-activated functionalities.</p><p>Here are some details, which, due to a mid-launch migration of the Guardian analytics platform, these statistics are extrapolated from Android user data:</p><p>— Over the course of the night, the alerts drove over 800K page views to the election night live blog and pages containing a full breakdown of results.</p><p>— Users could engage with the alert in three ways, which 74% of them did. Of that, here’s what they tapped on:</p><ul><li>The alert itself, which led to the live blog. Users tapped an average of 4.5 times throughout the night.</li><li>The Live Blog button. Users tapped an average of 2 times each.</li><li>The Full Results button. Users tapped an average of 2.5 times each.</li></ul><p>In keeping with previous experiments, we also sent out a follow-up survey to our users seeking qualitative feedback. We sent the survey at 3pm ET the Friday following the election via an app alert to all subscribers to the election-night notification who had not since opted out. We received more than 6,000 responses.</p><p>Overall, the alert received extremely high marks in the survey. An overwhelming majority of users thought the alert was useful, clear, effective and convenient. Nearly all respondents (98%) said they would definitely or maybe sign up for the alerts again.</p><p>In terms of usability, around 70% of respondents said they expanded the alert and also knew how to stop it if they wanted to opt out. Even more respondents, around 80%, reported knowing that the alert would automatically update, which is incredibly encouraging to hear when we’re considering integrating even more interactivity and content into the expanded view.</p><p>The data visualization graphic was popular among respondents, with 70% saying that it was useful, and another 56% saying that it was clear and scannable.</p><p>In terms of what users would have liked to have seen more of, they said they would have appreciated more data overall — including state-level information, projections and popular vote count.</p><p>On effectiveness:</p><ul><li>84.2% of our survey respondents told us that they found the notification effective or very effective at providing a convenient view of the results’ progress.</li></ul><p>On engagement:</p><ul><li>Upwards of 70% of users tapped through on the alert at some point throughout the night, either by tapping the alert itself, or one of the action buttons. That’s very similar to the engagement we saw with the Brexit live data alerts, when 77% of subscribers tapped on the alert at some point during the event.</li></ul><p>We’ll be following this post up with more about what we learned creating and deploying this new notification format. Stay tuned.</p><p>How did you follow the US elections? Let us know what you think. Send us an email at innovationlab@theguardian.com.</p><p><em>The Guardian Mobile Innovation Lab operates with the generous support of the </em><a href="http://knightfoundation.org/"><em>John S. and James L. Knight Foundation</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87bafbcf510" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-guardian-mobile-innovation-lab/building-the-guardians-live-elections-notifications-87bafbcf510">Building the Guardian’s Live Elections Notifications</a> was originally published in <a href="https://medium.com/the-guardian-mobile-innovation-lab">The Guardian Mobile Innovation Lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>