dangerzone
dangerzone copied to clipboard
Explore how to Simplify Save Options
From user research we found that it's not immediately clear to the user where the document will be saved. The save dialog need to be simplified and clarified. The feedback came from the 0.3.2 versions as well as the 0.4.0 version:
Notes / Evidence
During user testing some users were confused about the location of where the docs were and another wanted to change the location but couldn't find the option:
0.3.2 | 0.4.0 |
---|---|
it looks like it's saving it to Downloads. I guess I just don't know if the original document was stayed in the downloads folder and never made it on something else. | So where will the safe document then be saved? |
Does it default to like "name-safe" or is that something which is because you already preloaded it that way? | I can't see an option there if like if you wanted to save it somewhere else. |
"I'm wondering where it's going to save it to as like the default" | (same also applies in this version) |
"safe safe". There's two words... this word safe is in there twice. |
UX (initial) Proposal
These were some of the options originally proposed by the UX designers:
(assumed) User Goals
Make sure the user knows where the original file is (for preservation purposes) Make sure the user doesn’t open the malicious file
Current Options Breakdown
Current Save option | UX Proposal | What the user has to think about |
---|---|---|
☑️ Save as [document]-safe.pdf | ☑️ Add ‘safe’ to the end of file name / ☑️ Add ‘safe’ to the start of file name | Ending of safe files (or start) |
- | ☑️ Edit file name yourself | Name of saved file |
🔘 Move original documents to ‘unsafe’ subdirectory | ☑️ Create and move unsafe document/s to a folder called ‘unsafe’ | Where Unsafe files are saved (*) |
🔘 Save safe PDFs to [choose…] | Save new ‘safe’ document/s to [choose…] | Location of the safe files |
(*) we have a caveat here: currently if the file fails to convert, it will stay in the same place, potentially confusing users and leading to them mistakenly opening the malicious file.
Conceptual Model of Dangerzone Conversion
Dangerzone currently moves files in two ways:
- It creates a new safe file with prefix / suffix (optionally in a different location)
- (optionally) It moves the unsafe file to a new location