Skip to content
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.

UX for image element source #1523

Closed
xmatthewx opened this issue Apr 16, 2015 · 7 comments
Closed

UX for image element source #1523

xmatthewx opened this issue Apr 16, 2015 · 7 comments
Assignees
Labels
Milestone

Comments

@xmatthewx
Copy link
Contributor

UX for image selector (photo, gallery, uploader) is probably done already. Review and add clean set of notes to the build deck.

@xmatthewx xmatthewx added this to the Alpha 2/2 milestone Apr 16, 2015
@xmatthewx
Copy link
Contributor Author

Consider in tandem with loading indicators #1539

Will camera and gallery failures be handled by Android? cc @thisandagain

@flukeout
Copy link
Contributor

First UX pass for web image search

Behaviour

  • At first, all search options are visible
  • After a search is made, options disappear into "gear" menu
  • Tapping an image returns to tile editor with image source changed

image

Questions

  • What other options are important
    • Animated gifs?
    • Illustration vs Photo
    • Predominant color or Grayscale
  • Can we pre-populate the results?
    • Previous searches
    • Last used in other project
    • Autocomplete on search term
    • Search as user types or search when they explicitly finish typing
  • Alternate image result layouts?
  • What are some good benchmarks to investigate
    • Pic Collage
      • Starts with list of tappable popular search terms
      • Gifs vs Images is main category choice
      • Ability to select and add multiple images at once
      • Autocomplete suggests search terms
      • Tap image to select, tap Checkmark to add
    • Google image search on mobile

Content Types
In general, I think the two main image types will be backgrounds and stickers.

  • Backgrounds - large, beautiful images that serve as the backdrop for page content
  • Stickers - small images with transparent backgrounds

@xmatthewx
Copy link
Contributor Author

We should have @cadecairos investigate search services after he finishes his other API work to help figure out these parameters.

@thisandagain
Copy link
Contributor

I'd prefer to keep our UX exploration constrained to what is in-scope for v1.0 as we have a pretty heavy workload already. Let's make sure UX is nailed for beta and RC ... if we want to get a jump start on things I'd prefer to see movement on desktop.

@xmatthewx
Copy link
Contributor Author

@flukeout - for camera and gallery selector on mobile, can we call this done? I filed issue for search in the desktop repo.

I'm assuming that camera and gallery failures will be handled by Android. Notice for upload failures tracked in #1540

@thisandagain
Copy link
Contributor

Yup, we'll use the OS-level camera and gallery. Building up that SOW in #1615

@flukeout
Copy link
Contributor

flukeout commented May 1, 2015

Closing since not currently in scope, we'll make a new ticket down the road.

@flukeout flukeout closed this as completed May 1, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants