I2P UX Research
Installation & New User Onboarding
In 2020 the I2P UX team worked with Simply Secure on a usability sprint to assess user interaction with the I2P website. Many changes were applied, however, feedback has indicated that there are still issues with some aspects of new user onboarding.
This year we have expanded our team thanks to the BASICS project (Building Analytical and Support Infrastructure for Critical Security tools), and not only revisiting the new user onboarding, but we are also expanding the scope to include onboarding for developers and researchers. The goal will be to present an improved information architecture.
Research and Feedback
Homepage
People felt that the word “Get” is misleading on the download button on the homepage because the install process includes having to download Java first. Suggestion: change the call to action text on the download button to “Get Started with I2P”
Additionally , the “download” does not download the software instantly, it leads a user to a Download page. This seemed confusing that there were so many links to click.
Suggestion: have the link from the Download button go to a Getting Started page.
Download Page
People did not understand the mirror , sig or SHA options.
Suggestion: add a “what is this?” link that will provide more information or a tool tip.
“When I click the “Get I2P” button or “Download” on the homepage, I am brought directly to the Mac download section, so I don’t see the “Getting Started / Basic Steps” paragraphs above. I am just now seeing that I have to install Java and “Install/Configure a Browser(Optional).” Seems like the browser config is optional?”
OS detection was added to the download button on the Home page. The issue is that this causes the information at the top of the download page where direction is given to download Java to be missed. Also, a properly configured browser is required, and not an option, so messaging here needs to be fixed.
Suggestion: move all information into OS specific sections with clear directions to install Java.
“For the Mac download, my eyes glaze over the text underneath the green button. I don’t understand terminal or command line install so I ignore all of that. I just click on the green button.”
Suggestion: choose and focus on one download path and present other options more clearly.
Install Process (OSX)
“Can’t open file when double clicking download because Mac doesn’t recognize developer, could have malware.”
The Mac install guide will be included on the site so that this message will be presented in a way that explains why this happens rather than creating a “back out” reaction for people due to malware messaging.
“I2P is not “officially” distributed in the Apple Appstore. If you download files online, they can contain viruses. To protect users this message appears. However, this site is officially operated by I2P and does not contain viruses” Has been suggested as an option.
“The information on the post-install page is not relevant to Mac (mentioned previously on the UX research), there are Windows screenshots? Lots of jargon too. Not sure how much of the content needs to be geared towards developers vs non-technical people”
The Post-install instructions are incomplete and assume admin capabilities and network knowledge. There are references to sharing bandwidth and opening ports so that your router is not firewalled. Since adjusting NAT settings are not things that an average user needs to do to participate in the network, these asks are not relevant as part of the install process, and additionally add more steps and potential areas to back out since the install process in itself is so many steps. The suggestion is to move these network specific instructions to the documentation process for network contribution and advanced configuration. It should be stated also that “install” as a process should only have instructions to follow that have to do with installing the software.
“Text blocks are long. Depends on how much detail you want to give to the users because they might not need to know some of this information. Depends on goal of page/guide, right now your goal is to get it installed. The other stuff could be put in a troubleshooting section or add a tip/note that says ‘for bandwidth amount this is normal’ for reassurance.”
Suggestion: Reduce amount of text in the steps. Add tips or note boxes for things like the bandwidth.
Goals for Improvement / Improvements Introduced and Tested in Wireframe process
- Continuing to pare down the jargon and dense information is a big goal. Removed jargon-y instructions in the OS boxes on the download page.
- Removed links to sections and pages like Release Notes, System Updates, etc. and placed them in more appropriate places without cluttering the Getting Started flow.
- Call-to-action button on homepage takes you to a newly created Getting Started page which includes an overview of basic steps for downloading and installation. Getting Started wireframe is in the making.
- The multiple steps for getting started (Java and/or I2P download, install, configure) were condensed and made clearer, simpler. Downloading Java beforehand is important and made much more obvious! The tricky thing about this is that it couldn’t be the absolute first step because only Mac, Windows and Linux require the Java download whereas other OS like Android does not. It is a delicate balance of making it obvious but also not confusing users of different operating systems and making users read and wade through lots of information.
- Continue improving the flow. Remove extraneous links, reduce number of new pages/links user has to open. Make the progress more obvious to match Getting Started. Keep the user from feeling lost. Reduce unnecessary information.
- Incorporate installation guide with screenshots as part of the steps. Working on simplifying this guide and making it clear and easy to follow.
- Working on making the flow of steps and pages going from download java & i2p > install java & i2p > configure browser more streamlined, easy to follow without getting lost, confused, or in a “dead end” as one usability test user put it.
Summary of Key Findings
- Make homepage green button go straight to Getting Started page instead of Download page. Change the call-to-action text to match, i.e., ‘Get Started with I2P’
- Improve the Getting Started page and text/links in the cards.
- Downloading Java needs to be much more obvious. Put bigger download link and icon for Mac, Windows, Linux download boxes.
- Users were confused by Firefox Privacy Add-On and Firefox Browser Configuration. Change this.
- Users were confused by Install Wizard screenshots and the numbers 1 2 3 4 5 6. Change this.
Next Steps
Based on the first round of feedback, many changes have been made to improve the Installation /Getting Started process, including what was mentioned above. We will go through more rounds of usability tests to test these changes and get more feedback.
An updated Style Guide will be created during this process, which will include attention to easier to read fonts, illustration styles, and expanded colour options.
Installation Guides
Browser configuration and the inclusion of the I2P in Private Browsing extension for Firefox will include better visual mapping by browser. This way users can quickly and easily locate the information that is relevant to their configuration choice.
“Suggestion: Put all the browser config steps on one page like it currently is, to keep user from opening new pages and jumping back and forth and feeling lost in the steps/getting stuck in a dead end”.
“Users get freaked out when screenshots do not match exactly — use only essential screenshots”
“Suggestion: Add icons for browser for visual interest and break up text.”
“Suggestion: Add numbers for each step of the browser configuration.”
Thank you to everyone who has participated in this process during the past weeks!
Lucie & Sadie
