Features

Collection Types

  • App Wishlist. The app wish list is a collection that every user has by default. The app wish list allows the user to save apps to install later or on another device and is intended for personal use.
  • Custom Collections. Custom collections are all other collections that a user creates themselves. These collections can be shared with the Marketplace community.

Collection Elements

App Wishlist

  • Graphic
  • Avatar of the user who created the collection
  • Collection title “My App Wishlist”
  • App (app icon, name, developer, content rating, review rating, price button)

Custom Collection

  • Auto-generated graphic
  • Display name of user who created the collection
  • Avatar of the user who created the collection
  • Collection title
  • Collection description [optional]
  • App (app icon, name, developer, content rating, review rating, free button)

Collection Features

App wish list features

  • Ability to add apps from app details screen
  • Ability to remove apps

Custom collection features – for collection creator

  • Ability to add apps
  • Ability to make collection visible to all of Marketplace or keep hidden
  • Ability to view statistics on a collection (shares, views, upvotes)
  • Ability to remove apps
  • Arrange the order of apps
  • Ability to delete a collection

Custom collection features – for collection consumer

  • Ability to share collection
  • Ability to upvote the collection
  • Ability to flag the collection for abuse

Collection Visibility

Collections that are made public by their creators will be visible on the following screens

  • "Community" screen accessible via top level navigation
  • As modules in the feed chosen by the editor
  • Category screens (P2)
  • Search result screens

Visibility rules

  • A collection must have three or more apps to be publicly visible on the Marketplace
  • If an app in a collection is not available in the user’s region, by the user’s operator, or on their device (mobile use case), the user will not see that app though they will be able to see the rest of the apps in the collection.
  • If none or less than 3 of the apps in the collection are available in the user’s region, the user’s operator, or on their device (mobile use case) the user will not see that collection.
  • Proposal: Precompute visible collections by the common device profiles so the filtering doesn't have to be done in real time.

Preventing/Handling spam and offensive content in visible collections

  • Do not feature new collections prominently (i.e. on the homescreen). Make new collections available but only on community screen. Once the collection receives a good reputation (many views, many installs from views, likes, etc.) allow it to be featured on the home screen.
  • Allow users to flag content for abuse. If collection receives 3 abuse flags remove it from "Community" screen.
  • If a user posts a url in titles or description it should not be clickable. (main source of spam for AMO)
  • Auto-flag suspicious collections that appear to be spam and have them added to a review queue
  • Filter for users creating many, many collections (100s of collections)
  • Filter for users frequency of collection making (100s of collection in small amount of time)
  • Filter for duplicate collections (often spam bot)
  • Create a black list of banned users