Skip to content

Product: Collections, Shareable bot lists

Rebecka Z edited this page Apr 20, 2018 · 1 revision
name signoff?
product rz
design aq
dev b,b,e,p,p,
stakeholder sc

Goal:

Create a feature that allows users to create/organize/share a list of bots.

Product Requirements:

  1. User should be able to create a list of bots known as a "Collection".
  2. Users should be able to add any public bot to a collection from the bot profile, even if they do not own the bot profile.
  3. Only public bots can be added to a collection. The same bot can be added to more than one collection.
  4. If a public bot becomes private, the bot is automatically removed from the collection. The same would happen if the bot is deleted.
  5. A user can’t add the same bot twice to a collection.
  6. If a user is blocked by another user, all related bots created from that user should be removed from their collections. The user should not receive any notification that bots were removed.
  7. When a collection is created, a created notification should appear in the hs. Creation notifications work like bot created notifications. Where all of a user's followers will receive the notification including th collection creator. This is being removed.
  8. The HS card notification should show the title of the collection and the cover image of the collection. The metadata bar can be completely removed or replaced with other details (please explore).
  9. User should be able to title the collections.
  10. User should be able to order their bots in the collection. (A lot about collections is giving the superuser a chance to showcase their experience, they should be able to order them. The more control they have over this, the more likely the collection will propagate)
  11. A collection can have up to 50 bots. (MVP)
  12. The collection show show the "collection creator"
  13. When a collection is created by an owner, it is automatically saved to the owner’s list of collections.
  14. Owner should be able to edit a collection.
  15. Owner should be able to delete a collection.
  16. User should be able to unsave a collection
  17. Title and note changes will not create any related HS notification but should update in place
  18. A deleted collection should be removed from the HS
  19. Users should be able to share a collection.
  20. When a user shares a collection the receiving user should receive a HS notification and a push notification.
  21. Like bots, users can share collections with friends.
  22. When a receiving user receives a collection via share or creation notification they should be able to save it.
  23. A users collections should appear on their user profile.
  24. Collections cannot be private (MVP)