Milestone 7: User testing and Further Iteration

M7

From May 18 to May 29th, we continued testing with users and iterating on the product. For the story of what we've discovered, check out the slide deck from our presentation. The rest of this page seeks to elaborate on the material in the deck and fill in the detail for some topics the presentation could only touch on.


Consent Form

Consent form

What glmpse needs...

Starting on May 18th, glmpse was an effective way to get a 4-second video from a friend. But the users deserve more out of glmpse request. We want a glmpse request to turn into an interaction that feels complete and full. We don't want users feeling cut-off or for them to have to use other mediums (text, phone, email) to complete an interaction that began on glmpse.
With this in mind, we feel the need to enhance some aspects of our current design.

Testing setup

After getting our first submission rejected from the App Store, we continued using TestFlight to deliver our app to test users. Test users downloaded the app remotely and mostly used it without supervision or intervention from the dev team. We also conducted sessions in which we watched test users complete tasks on the app, and we interviewed test users.

users-graph

We've added test users continuously in the past two weeks, but most test users were added in three big spurts that corresponded to major new releases of the app. Overall, we tested with 30 distinct users.

videos-requests

After resetting the database of glmpse requests on May 18, we've processed 262 requests (141 from test users) and 260 video responses (117 from test users).

Functional Iteration

The most important changes we implemented, tested, and iterated on involve the inclusion of text prompts and enabling commenting on a provided video. For the full story on these features, check out our slide deck linked above. This section describes other important changes we made to the app.

Re-engineered on-boarding process

new-user
Since test users are downloading and launching the app remotely, we needed a better way to help them understand the app and its usage. Many test users had very little context for the app and, in the extreme case, had only exchanged a few emails with a dev team member. We decided to use the medium to help them get oriented and give them something actionable immediately upon their first log-in. Upon sign-up, two things happen automatically:

  1. We (TeamGlmpse) send the new user a stock glmpse that explains the app and how to do things
  2. We (TeamGlmpse) send the new user a request for a glmpse so they can get a feel for the experience of recording one
  3. .
The picture above shows the feed a new user sees -- an incoming explanatory glimpse and our request.

Reworked UI

With new requests, videos, or comments coming in, a user's feed it continuously changing. It soon became clear we needed better ways for users to know what's up. Among the questions we need the UI to answer for the user are:

The UI we are currently using displays all of a user's glimpse interactions in a unified feed, sorted by date. The status of each request is indicated by the triangle to the left of the request. We also use push notifications to notify a user of new glimpse requests, glimpse responses, and comments.
All other parts of the app have also gotten their UI revamped at least twice so far. For example, we improved the video recording page by displaying the prompt above the camera feed and visually showing users how far into the recording process they are (by having the red recording circle fill in as recording progresses).

Variable-length video recording

During testing, we soon realized that different kinds of requests require different video durations to fulfill. Some requests require just a quick facial expression while others are more involved. Four seconds is not a size that fits all, and when a video is only a few seconds long, a second or two more or less makes a huge difference. To enable flexibility of requests and to empower the glimpse provider to have more control over the glimpse they produce, we extended the maximum video duration to 10 seconds and now allow glimpse providers to stop the recording early if their glimpse requires less time.

What glmpse will do...

Design Implications

Looking forward, there are a number of features we're planning to implement to address the problems we've found in user testing, and also just to explore further possibilities with Glmpse: