5 ms·

Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it

Thanks for the reply. Adding a "cloud" icon to a button called "Save" does not make it clearer, it makes it contradictory (does it save it or does it upload it?). It's very clear based on the design of the interface that your primary goal is to get people to upload their screenshots to your servers. The "save" button is the only one with a label. The others are icons only. The "save" button is 3x as big as the other two. The "save" button is the only button with any color (the others are black & white). Also note that the current "save" feature (which uploads the screenshot to mozilla servers) actually does the opposite of saving them because after 2 weeks they will be deleted. I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? And when they hit "save" in microsoft word or whatever, they think the document is going to microsoft servers? "Save" means put it in my local storage. "Download" means copy some file from a remote server onto my local storage. "Upload" means copy it from my local storage to a remote server. I also just realized that clicking the "save" button clobbers whatever is in my clipboard. https://screenshots.firefox.com/oFTVibyVnGx7LPAl/news.ycombinator.com https://screenshots.firefox.com/oFTVibyVnGx7LPAl/news.ycombi...

saberworks 9y ago
After using it to actually upload that shot, I just realized it captured and shared much more than just the screenshot. It captured and shared the page title and domain of the page I took a screenshot of. That seems like quite the security risk given that I wasn't notified such was going to be shared. Imagine if I'm working on a dev server or a private place on a public server. It seems that when people want to share a screenshot, they want to share just the screenshot in many cases.
ianbicking 9y ago
> I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? More or less, yes, if more people understand one design than another, then the one that more people understand is the right one. We're generally shooting for more than a majority though, we'd want most people to understand the interface, and would also take negative reactions into account. In our past studies we found people generally understood the buttons well enough, and specifically it was obvious after first use what was happening. But we only compared the current buttons to one other option (which didn't compare well), so it wasn't a very thorough test. There's more overhead in updating this interface than some others, since we have to get updated translations (to more strings than just the button) and change all our onboarding, which is why we've kind of left it be until we can look at the full set of buttons more closely.
- saberworks 9y ago
  Haha I am completely dismayed. So that means if I use File -> "Save Page As..." I can look forward to that eventually sending my entire page to your servers ;) Again thanks for your replies and hopefully they can be more clear in the future (without being incorrect). And just in case I have sounded like a jerk, I really do love Firefox and I have been using it since it first came out as Phoenix. I appreciate the work you all put into it even if my above comments didn't make that clear. I actually used the Mozilla Suite before that, too. I still have, wear, and love my dinosaur head t-shirt I ordered from the mozilla store soooo long ago. https://upload.wikimedia.org/wikipedia/commons/thumb/7/74/Mozilla_Foundation_logo.svg/1024px-Mozilla_Foundation_logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/7/74/Mo...
  - teresonos 9y ago
    This seems to be one of those "dark patterns" in design, where they try to persuade someone to perform a certain action. At the very least, change it to "Save to Cloud" and "Save to Disk." But to be really clear, "Upload and Share" is definitely the way to go.
- cookiecaper 9y ago
  One of Mozilla's major value propositions is a privacy and security focus. Lots of people are interested in Firefox because it doesn't stream tons of data about browsing sessions upstream. It should always be obvious when a user is uploading information to the internet; the intuition on snipping/screenshot tools is that they perform actions locally. I take screenshots of internal graphs, admin pages that may contain pseudo-private endpoints and admin account information all the time ("Logged in as $ADMIN_USER", account numbers with vendors, etc.). Sharing those in a private chat or email is a big part of my screenshotting use case. People screenshot a lot of private data. I don't think Mozilla is wise in making "send your image to a public bucket protected only by the obscurity of its URL" the default behavior, at least not without making it obvious that this is what's happening. This sneaky exfiltration of private data is a large part of what people hate about Google and Facebook. Maybe there could be an opt-out on first use? I get that your average grandma isn't going to understand the distinction and will want something she can share (but she's also probably just trying to get to email or Facebook anyway), but this is a real potential security problem for your users.

saberworks 9y ago

After using it to actually upload that shot, I just realized it captured and shared much more than just the screenshot. It captured and shared the page title and domain of the page I took a screenshot of. That seems like quite the security risk given that I wasn't notified such was going to be shared. Imagine if I'm working on a dev server or a private place on a public server. It seems that when people want to share a screenshot, they want to share just the screenshot in many cases.

ianbicking 9y ago

> I'm not convinced "user research" is the best way to go here. If the majority of your selected users think "save" should mean "upload to mozilla" does that mean they're right? More or less, yes, if more people understand one design than another, then the one that more people understand is the right one. We're generally shooting for more than a majority though, we'd want most people to understand the interface, and would also take negative reactions into account. In our past studies we found people generally understood the buttons well enough, and specifically it was obvious after first use what was happening. But we only compared the current buttons to one other option (which didn't compare well), so it wasn't a very thorough test. There's more overhead in updating this interface than some others, since we have to get updated translations (to more strings than just the button) and change all our onboarding, which is why we've kind of left it be until we can look at the full set of buttons more closely.

saberworks 9y ago
Haha I am completely dismayed. So that means if I use File -> "Save Page As..." I can look forward to that eventually sending my entire page to your servers ;) Again thanks for your replies and hopefully they can be more clear in the future (without being incorrect). And just in case I have sounded like a jerk, I really do love Firefox and I have been using it since it first came out as Phoenix. I appreciate the work you all put into it even if my above comments didn't make that clear. I actually used the Mozilla Suite before that, too. I still have, wear, and love my dinosaur head t-shirt I ordered from the mozilla store soooo long ago. https://upload.wikimedia.org/wikipedia/commons/thumb/7/74/Mozilla_Foundation_logo.svg/1024px-Mozilla_Foundation_logo.svg.png https://upload.wikimedia.org/wikipedia/commons/thumb/7/74/Mo...
- teresonos 9y ago
  This seems to be one of those "dark patterns" in design, where they try to persuade someone to perform a certain action. At the very least, change it to "Save to Cloud" and "Save to Disk." But to be really clear, "Upload and Share" is definitely the way to go.
cookiecaper 9y ago
One of Mozilla's major value propositions is a privacy and security focus. Lots of people are interested in Firefox because it doesn't stream tons of data about browsing sessions upstream. It should always be obvious when a user is uploading information to the internet; the intuition on snipping/screenshot tools is that they perform actions locally. I take screenshots of internal graphs, admin pages that may contain pseudo-private endpoints and admin account information all the time ("Logged in as $ADMIN_USER", account numbers with vendors, etc.). Sharing those in a private chat or email is a big part of my screenshotting use case. People screenshot a lot of private data. I don't think Mozilla is wise in making "send your image to a public bucket protected only by the obscurity of its URL" the default behavior, at least not without making it obvious that this is what's happening. This sneaky exfiltration of private data is a large part of what people hate about Google and Facebook. Maybe there could be an opt-out on first use? I get that your average grandma isn't going to understand the distinction and will want something she can share (but she's also probably just trying to get to email or Facebook anyway), but this is a real potential security problem for your users.