Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: Not apparent that "Download Hash" uses clipboard #1135

Closed
machawk1 opened this issue Sep 19, 2019 · 3 comments · Fixed by #1419
Closed

UI: Not apparent that "Download Hash" uses clipboard #1135

machawk1 opened this issue Sep 19, 2019 · 3 comments · Fixed by #1419
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/design-content Content design, writing, information architecture topic/design-ux UX strategy, research, not solely visual design

Comments

@machawk1
Copy link
Contributor

I am glad to see a native UI within the Finder and was curious as to the purpose of the "Download Hash" entry. When I select it, I am told the hash in my clipboard is not valid. I was not aware that the clipboard was going to be used when selecting this menu item. I anticipated some UI to appear allowing me to somehow specify the hash as input.

It would be helpful if the underlying function of this menu option were more apparent without having to select the option and being told of invalid input without knowing the source of the input. Something either indicative that the clipboard will be used or providing some other UI for the user to specify a source of the hash.

ipfs-desktop 0.9.2
macOS 10.14.6

@hacdias
Copy link
Member

hacdias commented Sep 22, 2019

Thanks for the heads up @machawk1. We should definitely add some information. Perhaps change to 'Download CID from clipboard' or add a little information below... I'll try that out

@hacdias hacdias added the UX label Sep 27, 2019
@hacdias hacdias mentioned this issue Sep 27, 2019
15 tasks
@hacdias
Copy link
Member

hacdias commented Sep 29, 2019

I tried adding additional text below but it doesn't look great... Other suggestion could be just changing the copy to something like 'Download from Clipboard' or 'Download CID from Clipboard'. However, that would make the menu much larger. Wdyt?

image

@machawk1
Copy link
Contributor Author

I agree, the long string in the menu item would be visually verbose.

Have you considered not using the clipboard for this functionality by default or rather, giving the user an option to specify the hash after selecting this menu item?

For example, the menu item could say "Download..." and when selected, display a modal with a text box (potentially pre-populated with the clipboard contents if applicable) providing the ability for the user to provide input (e.g., the hash).

Otherwise, neither "Download from Clipboard", "Download CID from Clipboard", nor the current "Download Hash" seem to capture the implemented functionality. Isn't ipfs-desktop download the payload at this hash/CID, not the hash itself? For example, if the identifier was a URI instead of a hash, one would not say "Download URI from clipboard", but something more akin to "Download webpage".

@hacdias hacdias mentioned this issue Nov 5, 2019
27 tasks
@jessicaschilling jessicaschilling added topic/design-content Content design, writing, information architecture topic/design-ux UX strategy, research, not solely visual design and removed UX labels Mar 30, 2020
@jessicaschilling jessicaschilling added exp/novice Someone with a little familiarity can pick up effort/hours Estimated to take one or several hours good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked labels Apr 8, 2020
This was referenced Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/design-content Content design, writing, information architecture topic/design-ux UX strategy, research, not solely visual design
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants