-
Notifications
You must be signed in to change notification settings - Fork 0
Product: Homestream Biz Logic
Rebecka Z edited this page Apr 20, 2018
·
1 revision
Items that need batch, are items that can't be a solo trigger notification for New Updates
because they don't provide New Update
value to the user. In other words, users expect to see a new card when they tap on New Update
Bot Related Action | HS Actions | Triggered when... | New Update Batching required? |
---|---|---|---|
Bot Created by Owner (visibility is set: public) | Bot creation notification, inserts at the top | User taps on New Updates CTA, user leaves HS | No |
Bot Created by Owner (visibility is set: private) | n/a | n/a | n/a |
Bot Created by a followed user (visibility is set: public) | Bot creation notification, inserts at the top | User taps on New Updates CTA, user leaves HS | No |
Bot Created by a followed user (visibility switched from public --> private) | Bot omits from HS | User taps on New Updates CTA, user leaves HS | Yes |
Bot Share (user shares bot) | Bot shared notification, inserts at the top | User taps on New Updates CTA, user leaves HS | No |
Bot Description Added, for the first time, may have to punt on this one until we can get some validation logic in) | Bot note added notification, inserts at the top | User taps on New Updates CTA, user leaves HS | No |
Bot Description Modification (existing description [note] modified) | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Bot Post: Post Added | Post notification, inserts at the top | User taps on New Updates CTA, user leaves HS | No |
Bot Post: Post Deleted | Post notification, omits from HS | User taps on New Updates CTA, user leaves HS | Yes |
Bot Modified: Post Added | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Bot Modified: Title Change | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Bot Modified: Address Change | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Bot Modified: Cover Image Change | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Bot Modified: Cover Image Added | Bot updates in place | User taps on New Updates CTA, user leaves HS | Yes |
Any user subscribes to bot | Bot updates in place | Updates in real time (as is) | n/a |
Any user unsubscribes from bot | Bot updates in place | Updates in real time (as is) | n/a |
Bot Modified: Deleted | Bot omits from HS | User taps on New Updates CTA, user leaves HS | Yes |
Account owner subscribes to bot | Account owner begins receiving only new events in HS | User taps on New Updates CTA, user leaves HS | n/a, see bot level rules |
Account owner unsubscribes from bot | Previous bot events stay within HS, but no new events | User taps on New Updates CTA, user leaves HS | n/a |
Account owner blocks user | All blocked user related info omits from HS | User returning from blocking flow | n/a |
Account owner unfollows a user | Previous bot events stay within HS, but no new events | User taps on New Updates CTA, user leaves HS | n/a |