CrossClave App
Secure Send Feature
Project Overview
From journalists, to pro-democracy advocates, to dissodents—for many of our users the stakes are indeed high. Many of these high-risk users expressed a need to share files with people in a more light-weight way.
Research
Can’t Crossclave already do this? Well, yes... kinda.
While onboarding a person as a team member-proper could solve this problem, user feedback highlighted several painpoints that render this seemingly simple solution ineffective.
- High security/privacy risk users are often working with folks that are understandibly leerie of app downloads and signup processes, no matter how secure/private the service claims to be. Web app for the win! 😎
- They wanted something quick, and simple... something as close to a share link as proper privacy/security will allow.
- While they would prefer a solution that allows for sending as well as receiving files securely, sending was the primary use case.
Mid fidelity prototyping
Much of the design and prototyping for this feature was done at a medium to high fidelity as much of the design was utilizing existing components in the app... insert twitter meme about skipping important UX steps 🙃
The feature is discoverable within the existing action menu for individual files within the CC file browser...
The recieving end UI is designed as a simple web app, as shown in the mobile browser mocks here.
Final Design
The final web app UI for the recipient side of the secure file send interaction is minimal and simple, while integrating some of the playful product illustration from the CrossClave app proper.
Reflection
Feedback as funneled through our customer success and sales teams indicate that Secure Send feeds two birds with one stone by:
- Allowing high security risk users to effectively share files without going through the full onboarding process for the recipeint AND...
- Also offers our less security focused users to light-weight file sharing experience