Mobile-generated desktop reminders

Patent metadata

Field	Value
Publication number	US-11599235-B1
Application number	US-202117523574-A
Country	US
Kind code	B1
Filing date	Nov 10, 2021
Priority date	Sep 21, 2021
Publication date	Mar 7, 2023
Grant date	Mar 7, 2023

Abstract

The present disclosure is related to receiving a communication (e.g., direct message, group message, calendar event, task, etc.) on a first device and providing an option to request that a reminder, which is associated with the communication, be presented a second device. For example, the communication may be presented via a mobile client, and the user may request that a reminder be presented via a desktop client (e.g., when the user is at the desktop client).

First claim

What is claimed is:

1. A method comprising:
rendering, for display via a mobile client, a first communication associated with a user account of a communication platform;
receiving a first request to render, for display via a desktop client associated with the user account, a first reminder associated with the first communication, wherein the first request to render the first reminder is based on an instruction from the mobile client;
rendering, for display via the mobile client, a second communication associated with the user account;
receiving a second request to render, for display via the desktop client, a second reminder associated with the second communication;
ranking, based at least in part on whether a channel, a user account, or direct message associated with the first reminder is identified as important, the first reminder higher than the second reminder;
determining that a state of the desktop client satisfies a condition; and
in response to the condition being satisfied, rendering, for display via the desktop client, the first reminder associated with the first communication with a higher priority than the second reminder, wherein an indication of the first reminder is displayed as a direct message from a non-user account associated with the communication platform.

2. The method of claim 1 , wherein:
the desktop client includes a desktop communication application; and
the state is based on one or more of the desktop communication application being open, launched, unhidden, or logged onto.

3. The method of claim 1 , wherein:
the desktop client includes a computing device; and
the state is based on one or more of the computing device starting up, waking, connecting to a network, establishing a communication protocol, or receiving an input.

4. The method of claim 1 further comprising, sending, by the desktop client and based on the condition being satisfied, an API call to a database including data associated with the first request to render the first reminder.

5. The method of claim 1 further comprising:
generating a third communication indicating the first request to render the first reminder was received; and
rendering, for display via the mobile client and in a thread with the first communication, the third communication.

6. The method of claim 1 , wherein the first communication includes an action item assigned to the user account.

7. The method of claim 1 , wherein ranking the first reminder and the second reminder is further based at least in part on whether the first reminder and the second reminder are associated with a channel, a user account, or another communication associated with the communication platform.

8. A system comprising:
one or more processors; and
one or more non-transitory computer readable media storing instructions that, when executed, cause the system to:
render, for display via a mobile client, a first communication associated with a user account of a communication platform;
receive a first request to render, for display via a desktop client associated with the user account, a first reminder associated with the first communication, wherein the first request to render the first reminder is based on an instruction from the mobile client;
render, for display via the mobile client, a second communication associated with the user account;
receive a second request to render, for display via the desktop client, a second reminder associated with the second communication;
rank, based at least in part on whether a channel, a user account, or direct message associated with the first reminder is identified as important, the first reminder higher than the second reminder;
determine that a state of the desktop client satisfies a condition; and
in response to the condition being satisfied, render, for display via the desktop client, the first reminder associated with the first communication with a higher priority than the second reminder, wherein an indication of the first reminder is displayed as a direct message from a non-user account associated with the communication platform.

9. The system of claim 8 , wherein:
the desktop client includes a desktop communication application; and
the state is based on one or more of the desktop communication application being open, launched, unhidden, or logged onto.

10. The system of claim 8 , wherein:
the desktop client includes a computing device; and
the state is based on one or more of the computing device starting up, waking, connecting to a network, establishing a communication protocol, or receiving an input.

11. The system of claim 8 , wherein the instructions further cause the system to send, by the desktop client and based on the condition being satisfied, an API call to a database including data associated with the first request to render the first reminder.

12. The system of claim 8 , wherein the instructions further cause the system to:
generate a third communication indicating the first request to render the first reminder was received; and
render, for display via the mobile client and in a thread with the first communication, the third communication.

13. The system of claim 8 , wherein the first communication includes an action item assigned to the user account.

14. The system of claim 8 , wherein ranking the first reminder and the second reminder is further based at least in part on whether the first reminder and the second reminder are associated with a channel, a user account, or another communication associated with the communication platform.

15. One or more non-transitory computer readable media storing instructions that, when executed, cause one or more processors to:
render, for display via a mobile client, a first communication associated with a user account of a communication platform;
receive a first request to render, for display via a desktop client associated with the user account, a first reminder associated with the first communication, wherein the first request to render the first reminder is based on an instruction from the mobile client;
render, for display via the mobile client, a second communication associated with the user account;
receive a second request to render, for display via the desktop client, a second reminder associated with the second communication;
rank, based at least in part on whether a channel, a user account, or direct message associated with the first reminder is identified as important, the first reminder higher than the second reminder;
determine that a state of the desktop client satisfies a condition; and
in response to the condition being satisfied, render, for display via the desktop client, the first reminder associated with the first communication with a higher priority than the second reminder, wherein an indication of the first reminder is displayed as a direct message from a non-user account associated with the communication platform.

16. The one or more non-transitory computer readable media of claim 15 , wherein:
the desktop client includes a desktop communication application; and
the state is based on one or more of the desktop communication application being open, launched, unhidden, or logged onto.

17. The one or more non-transitory computer readable media of claim 15 , wherein:
the desktop client includes a computing device; and
the state is based on one or more of the computing device starting up, waking, connecting to a network, establishing a communication protocol, or receiving an input.

18. The one or more non-transitory computer readable media of claim 15 ,

Assignees

• Slack Tech Llc
• Salesforce Inc

Inventors

• Alvarado Catherine Yesenia
• Balakrishna Madhu
• Bakshi Akshay
• Carlborg Beau
• Chmura Jon Papandreas
• Greenberg Ryan
• Bahk Vanessa

Classifications

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L67/306

  User profiles · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L51/224

  providing notification on incoming messages, e.g. pushed notifications of received messages · CPC title

• G06F3/0481 Primary

  based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance · CPC title