Briar Usability Study SplinterCon Berlin 2024

Hey everyone,


During the previous week, the Ura team had the chance to attend SplinterCon in Berlin. It was a three-day conference full of presentations, hackathons, and workshops, and during the last day, we had the opportunity to moderate a usability study session regarding Briar. Given the event’s restrictions on photos and video recordings, all findings were documented through written notes from both participants and our team. Prior to the study, participants were informed that their personal information would not be recorded, ensuring their privacy and consent. The study comprised four sections, beginning with a brief introduction to usability studies and an overview of Briar. Participants were then tasked with completing specific activities designed to test the application’s usability. The tasks and corresponding findings are detailed in the following sections alongside our recommendations on how to improve the user experience of Briar.

We are here posting our findings, which are probably known to some extent, but it might be helpful to validate these further based on the amount of people we tested with.

Task 1: Setup a Briar Account

After downloading Briar, the first task was to set up an account. We provided an Android mobile device for existing users and asked them to create a new account under an alias for testing purposes.

1. First Screen Experience: Users encountered challenges on Briar’s initial screen, which required entering a username. Participants were unclear about Briar’s purpose and how their data was stored or used. They also lacked an understanding of its security model, leading to mistrust and hesitation.

Recommendations:

  • Add a brief introductory screen explaining Briar’s purpose, data storage, and security model on the first screen they interact with (instead of the second screen).
  • Use visual aids or tooltips to clarify key concepts that might be unfamiliar with non-tech-savvy users.

2. Save Credentials Feature: Users did not realize Briar doesn’t store login credentials, causing confusion. They had to manually save passwords elsewhere, with many defaulting to weak passwords like simple numerical sequences.

Recommendations:

  • Introduce a password strength meter to encourage secure choices.
  • Add a notification reminding users to save their password securely.

3. Onboarding Process: Participants struggled to navigate Briar without guidance, finding the initial steps frustrating and unclear.

Recommendations:

  • Implement a guided onboarding process to introduce features step-by-step.
  • Provide optional tutorials or help links for additional support.


Conclusion: Enhancing the first screen, credentials handling, and onboarding can greatly improve Briar’s usability while maintaining its commitment to security.

Task 2: Add a Contact and Message Them

After creating an account, participants were tasked with adding a contact and messaging them. Briar offers two connection methods:

  • Add Contact from a Distance: Users share a link in a different chat, assign a nickname, and input the recipient’s link to connect remotely.
  • Add Contact Nearby: Users scan each other’s QR codes to connect in person.
We asked the participants to use both connectivity methods to connect with each other.

Findings:

  • Understanding Connection Methods: Participants found the differences between the two methods unclear, particularly regarding requirements like network type or Bluetooth.
  • Link Connection Issues: Users were confused about assigning nicknames and using external chats for connection. This added unnecessary steps and complexity and asked why they needed to give a nickname if the user had already provided a nickname.
  • QR Code Issues: The QR code method was time-consuming and frequently unsuccessful. Users questioned why both parties needed to scan two codes instead of one.
  • Connectivity Status: Participants were unclear about the meaning of UI elements, such as dots, and whether they indicated online status or new messages received.

Recommendations:

  • Simplify and clarify the connection methods, with clear instructions on requirements like network or Bluetooth.
  • Streamline the link connection process by removing unnecessary steps like assigning nicknames, or give a detailed explanation on why asking for a nickname is important.
  • Improve the reliability and speed of QR code connections and consider making it a one-sided process.
  • Update the UI to clearly differentiate indicators for user status and message notifications.


Conclusion: Refining the contact-adding process and addressing these usability issues can improve user satisfaction and reduce confusion, making Briar more accessible for first-time users.

Task 3: Create a Group Chat and add 2 Participants

After connecting with other participants, users were tasked with creating a group and adding two contacts. This task was completed successfully by those who managed to connect with others in the previous task.

Findings:

  • Unclear Group Types: Participants were confused about the difference between a private group and a forum, which impacted their ability to choose the appropriate option.
  • Connectivity Issues: Users did not understand why they couldn’t add someone already in a group or why they received messages from non-contacts. This inconsistency led to frustration and mistrust.
  • UI Ambiguity: The meaning of hashtags and their associated colors (red, green, gray) on the interface was unclear, leaving participants uncertain about connectivity status.

Recommendations:

  • Provide a clear explanation of group types during the creation process, highlighting the differences between private groups and forums.
  • Clarify group and contact connection rules with in-app prompts or tooltips.
  • Add a legend or tooltip explaining hashtag colors and their meanings on the interface.

Conclusion: Improving clarity around group functionality and connectivity status can enhance the user experience, reducing confusion and fostering trust in Briar.

Edited by Elio Qoshi