search

mozilla / webmaker-addons

Prototypes for add-ons. Gateways from browser to Webmaker.
http://mozilla.github.io/webmaker-addons/
4 stars 2 forks source link

Reveal & Enable Action #8

Open xmatthewx opened 9 years ago

xmatthewx commented 9 years ago

Users who find an image need to trigger the editing and sharing experience. Before they can do that, however, they need to know that it's possible!!

Some people who install the add-on will fully understand that and remember it later. Many or most will not. If we were omniscient, we could ping a user the moment they thought, "Huh, cool. Jane would love that image. It would be even cooler if...." How can we approximate that?

Flavors of See - Tap - Go:

  1. Right click - reveals context menu (totally hidden, not touch friendly)
  2. Long press - reveals context menu (hidden, fiddly)
  3. Hover on image - reveals icon button (pings a user nicely, desktop only)
  4. Tap image - reveals icon button* (interferes with site defaults)
  5. Mouse move - reveals buttons on all images, fade after delay (nice reminder, desktop only, probably annoying)
  6. Scrolling - reveals buttons on all images, fade after delay (nice reminder, can't scroll on short pages)
  7. Image in Region - icon button revealed when image passes through a region of the page like top 25% (can't scroll on short pages)
  8. Always On - show small, permanent icon buttons on images
  9. Activate plugin - make all images selectable or draggable to edit space (hidden in menus, disrupts browsing)
  10. other ideas? please share...

* An icon button added to an image would look similar to this, but way less ugly:

image-action

xmatthewx commented 9 years ago

My gut tells me we should start with Always On to make this thing totally accessible. If we gain users and those users complain, I will be happy. We can then explore more slick and less obtrusive options.