The Loki Project is a blockchain enforced mixnet that allows users to securely transmit and receive data and cryptographic tokens without malicious actors having insight into user data or activity. It is a registered Australian nonprofit that believes digital privacy and freedom of speech are fundamental human rights. This case study specifically centers around the redesign of their messaging application built from blockchain technology, Session. An application that differentiates itself from its competition via decentralized service node protocol, the app ensures a higher degree of privacy in its end-to-end encryption, as well as a higher resistance to hacking and other potential vulnerabilities found in other centralized service models.
Promote growth of the application through intentional and research driven design, ideally setting up the application for widespread adoption.
A completely redesigned user interface that sets Session apart from other encrypted messaging platforms, appeals to varying user types, all while exemplifying the company’s value proposition.
Contract UI/UX Designer
Prior to design, it is important to consider the purpose and context of the application. The main goal of an ecosystem analysis is to uncover potential motivations and examine where Session fits into a user’s overall flow of virtual communication, the different potential uses, as well as the societal context of the application. This acts as an anchor for the scope of the project. I chose to list out six different ‘WH’ questions (who, why, what, where, how, and when) and prioritized them by taking a hybrid approach from the User Centered Design Model and the Genius Model.
Based on market research, the three primary risks associated with performing any task on the internet include exposure to cybercriminals, the resale of information, or the risk of being unknowingly monitored by one’s own government or anyone who has access to the server where their data is being kept. While end-to-end encryption has risen as a potential solution, there are still vulnerabilities that may be exploited and it is still not a foolproof option for fully anonymous messaging or interactions. Along with an application that utilizes E2EE methods, a decentralized server would also serve to increase the integrity of the security protocols already in place. This coupled with lack of metadata collection would also be a selling point for demographics of users that have reported feeling watched by the government or an external presence, who feel that their information may be at risk, and who actively search for ways to increase their online privacy.
The competitive analysis examined what Loki Session’s direct and indirect competition is doing, and helped ideate what features the company could incorporate that would set it apart from its competition in a significant way, while further capitalizing on its value proposition. Reviews from the app store were also taken into consideration. My competitive analysis produced the following insights:
To fully understand the scope of the project, it is essential to conduct stakeholder interviews in order to minimize assumptions, provide clarity in terms of the ideal project outcome, and narrow the scope of the project. The stakeholder interview is also beneficial in ensuring that all necessary and governing parties are on the same page as to what is being created. Below are the recurring themes taken from the major stakeholders involved (CTO, CEO, CMO, and the Lead Mobile Developer).
Design and Branding
Feedback from Beta Users
Prior to the release of Session, its predecessor from which it was adapted, Loki Messenger, had a forum that allowed users to provide feedback in real time to the Session development team. This early feedback was critical to understanding what current users valued the most, and where they felt the app could improve. The biggest complaints were related to the apps usability, visual design, lack of clarity as to how to add contacts, and its obvious resemblance to Signal (the codebase from which it was originally forked from).
During the ideation stage, my priorities were to generate innovative ideas, identify necessary features for the initial MVP, and ensure consistency between stakeholder, development, and user expectations.
STEP 2: USER FLOW
One priority when I was brought onto the Loki team was improving their on-boarding process. I wanted to keep this as simple and straightforward as possible while also explaining what a public key and seed were. These are terminologies and phrases that are unique to the blockchain and crypto community that they hoped would be translatable to the average user, so I wanted to keep the flow as minimalistic and simple as possible.
Based on business goals, user goals, and technical/usability goals, I created a spreadsheet that outlined necessary features for the initial MVP, features that would be nice to incorporate, and future features that would help improve the application’s overall customer experience while taking into account specific user groups needs, start to finish. The spreadsheet can be viewed HERE.
Prior to sketching out initial prototype ideas, I decided to combine the idea of a site map with a Jobs to Be Done worksheet. Given that I was tasked with redesigning the app versus building it from the ground up, I was essentially reorganizing and clarifying information rather than thinking about what information had to be included at all. It was less of a challenge viewing what needed to be on each page and more of a challenge brainstorming how to visually convey task flows in a way that displayed hierarchy versus disorganized and scattered icons that conveyed a medley of different things. By creating a Task Analysis worksheet of the primary, secondary, and tertiary tasks I intended for the user to complete on any given page, it set the stage for low fidelity wireframing.
After establishing a clear hierarchy of information, I began to brainstorm ways in which blocks of information could be visually conveyed by sketching my initial ideas out on paper. These are my initial, low-fidelity wireframes in their barest form.
In terms of my design process, I tend to put my visual research last so my designs are not influenced by superficial design decisions. What I hoped to gain by creating an inspiration board was inspiration from other messenger UI’s in order to brainstorm how I wanted to scale the mobile app’s ui into a desktop application.
A design choice I very deliberately chose to incorporate for Session 1.0’s release, dark mode felt, not only enticing and mysterious, but also an embodiment of everything the app stood for: privacy, security, peace of mind. Given the redacted nature of the application’s branding, and the desire to capitalize on the brand’s primary value proposition of being a fully anonymous, decentralized messenger, I felt a dark mode would be fitting for the app’s initial release, while a light mode would be a delightful feature that would accompany the app’s evolution from 1.0 into 2.0. Dark mode being the application’s primary palette symbolized discretion, subtlety, and modernity, which are all qualities that the Loki Project hoped to convey with the release of Session.
I would say the hardest challenge when it came to this project was bringing together the ideas that every essential stakeholder had in order to craft a user experience that was clear, provided direct functionality, and also didn’t compromise when it came to properly explaining the technology behind the application. Part of the challenge was taking an application that had a very clear demographic of users with prior blockchain experience, and turning it into an app that would have the capability to appeal to the masses. This included rethinking the original design, swapping out iconography, and remaining receptive to criticism along the way (a designer’s biggest Achilles heel).