Object for pre- to post-meeting collaboration
Traditionally, meetings are widely utilized in business and personal communications, whether in-person and/or virtual. Organizing such meetings typically involves multiple exchanges of content and messages between users before, during, and after the meeting. In some cases, meetings may occur impromptu and may result in inefficient and unproductive collaboration. A collaboration object configured to enable users to dynamically collaborate before, during, and after a meeting is provided. In aspects, the collaboration object links content generated before, during, and after the meeting in a single location and provides functionality for concurrent multi-user interaction and synchronization of the content across applications. The collaboration object may be available from a variety of application platforms, enabling and persisting real-time editing and collaboration before, during and after the meeting.
1. A method for receiving a meeting invitation including a collaboration object, the method comprising:
receiving an indication from a user to generate a collaboration object associated with the meeting using a first application, wherein the collaboration object comprises an attendance tracker;
generating the collaboration object, the collaboration object comprising a portable interface providing functionality for concurrent multi-user interaction with content of the collaboration object in near real-time;
retrieving metadata from the collaboration object, wherein the metadata comprises information for customizing a first collaborative user experience (UX) for the first application and a second collaborative UX for a second application;
based on the metadata, causing the first collaborative UX associated with the collaboration object to be rendered via the first application;
launching the second application;
based on the metadata, causing the second collaborative UX associated with the collaboration object to be rendered via the second application, wherein the first collaborative UX and the second collaborative UX are different;
receiving a change to content associated with the collaboration object via the second application; and
automatically causing the change to be reflected in the collaboration object associated with the first application.
2. The method of claim 1 , further comprising:
automatically causing the change to be reflected in the collaboration object associated with a corresponding meeting in the user's calendar associated with the first application.
3. The method of claim 1 , wherein the collaboration object includes one or more content categories for receiving content associated with the meeting.
4. The method of claim 1 , wherein the receiving an indication from a user to generate a collaboration object associated with the meeting using a first application comprises receiving content to a content category selected from a plurality of content categories to be added to the collaboration object.
5. The method of claim 1 , further comprising:
receive a content item shared during the meeting via the second application;
automatically cause the shared content item to be associated with the collaboration object via the second application; and
automatically cause the shared content item to be reflected in the collaboration object via the first application.
6. A computer storage medium storing computer-executable instructions that when executed cause at least one processor to perform operations, comprising:
receiving an indication from a user to generate a collaboration object associated with a meeting using a first application, wherein the collaboration object comprises an attendance tracker and has associated metadata comprising information for customizing a first collaborative user experience (UX) for the collaboration object via the first application and a second collaborative UX for a second application;
generating the collaboration object, the collaboration object comprising a portable interface providing functionality for concurrent multi-user interaction with content of the collaboration object in near real-time;
launching, based on the metadata, the second application for hosting the meeting, wherein the collaboration object is accessible for concurrent editing via the second collaborative UX by a plurality of meeting participants;
detecting content shared by at least one meeting participant during the meeting;
automatically causing the shared content to be associated with the collaboration object via the second application; and
automatically causing the shared content to be reflected in the collaboration object via the first application.
7. The computer storage medium of claim 6 , the operations further comprising:
receiving user input to the collaboration object via the second application.
8. The computer storage medium of claim 7 , the operations further comprising:
automatically causing the user input to be reflected in the collaboration object associated with the first application.
9. The computer storage medium of claim 6 , wherein the collaboration object includes one or more content categories for receiving content associated with the meeting.
10. The computer storage medium of claim 6 , wherein the receiving an indication from a user to generate a collaboration object associated with the meeting using a first application comprises receiving content to a content category selected from a plurality of content categories to be added to the collaboration object.
11. A system comprising:
at least one processing unit; and
at least one memory having a plurality of instructions stored thereon that, when executed by the at least one processor, cause the system to:
receive an indication from a user to generate a collaboration object associated with the meeting using a first application, wherein the collaboration object comprises an attendance tracker;
generate the collaboration object, the collaboration object comprising a portable interface providing functionality for concurrent multi-user interaction with content of the collaboration object in near real-time;
retrieve metadata from the collaboration object, wherein the metadata comprises information for customizing a first collaborative user experience (UX) for the first application and a second collaborative UX for a second application;
based on the metadata, cause the first collaborative UX associated with the collaboration object to be rendered via the first application;
launch the second application;
based on the metadata, cause the second collaborative UX associated with the collaboration object to be rendered via the second application, wherein the first collaborative UX and the second collaborative UX are different;
receive a change to content associated with the collaboration object via the second application; and
automatically cause the change to be reflected in the collaboration object associated with the first application.
12. The system of claim 11 , the plurality of instructions when executed by the at least one processor causing the system to:
automatically causing the change to be reflected in the collaboration object associated with a corresponding meeting in the user's calendar associated with the first application.
13. The system of claim 11 , wherein the collaboration object includes one or more content categories for receiving content associated with the meeting.
14. The system of claim 11 , wherein the receiving an indication from a user to generate a collaboration object associated with the meeting using a first application comprises receiving content to a content category selected from a plurality of content categories to be added to the collaboration object.
15. The system of claim 11 , the plurality of instructions when executed by the at least one processor causing the system to:
receive a content item shared during the meeting via the second application;
automatically cause the shared content item to be associated with the collaboration object via the second application; and
automatically cause the shared content item to be reflected in the collaboration object via the first application.