Exemplary embodiments relate to the application of coordinated or cooperative effects to a coordinated activity. A coordinated activity protocol is provided for synchronizing interactive effects and experiences across multiple devices. The protocol allows effects to be initiated and coordinated on multiple devices via a real-time communications (RTC) channel. Messages may be exchanged to cooperatively initiate the effect, and (once initiated) generic data may be exchanged via application programming interface (API) calls. According to some embodiments, the coordinated activity is a shared video experience, such as a video conference or shared video-watching experience. According to other embodiments, the coordinated activity relates to other types of experiences, such as single- or multi-player games, shared book reading, communal interactions with a photo album, etc.

A method, system and computer program product for user interface action recommendations. According to the method, a target segment in a target document is determined. Correlation degree between the target segment and at least one source segment in at least one source document is determined. At least one recommended source segment is provided from the at least one source segment based on the correlation degree for a user interface action, such as copying for pasting the target segment.

System and method for facilitating management of a time-varying resource pool are provided. The system includes a processor and a memory coupled to the processor. The memory stores processor-executable instructions that, when executed, configure the processor to: obtain a time-series data set including data entries associated with one or more consumed resources; identify one or more recurring resource allocations based on recurring data entries of the time-series data set; identify additional resource allocations based on irregularly-timed data entries of the time-series data set; determine a forecasted resource pool value based on a combination of the identified recurring resource allocations and the additional resource allocations; and upon detection of a trigger condition, generate data for display, via a user interface, a scaled resource allocation value based on the forecasted resource pool value.

An issue tracking system configured to track issues, tickets, or tasks is described herein. The issue tracking system may be used to create, modify, and delete issue records during a live meeting or event. The issue tracking system may be adapted to determine a likelihood of user attendance or user proximity and, in accordance with the likelihood exceeding a threshold or meeting a criteria, suppress transmission of notifications to a subset of user devices. Normal or unsuppressed notification transmission is maintained to another subset of user devices.

Implementations set forth herein relate to intervening notifications provided by an application for mitigating computationally wasteful application launching behavior that is exhibited by some users. A state of a module of a target application can be identified by emulating user inputs previously provided by the user to the target application. In this way, the state of the module can be determined without visibly launching the target application. When the state of the module is determined to satisfy criteria for providing a notification to the user, the application can render a notification for the user. The application can provide intervening notifications for a variety of different target applications in order to reduce a frequency at which the user launches and closes applications to check for variations in target application content.

In order to provide agile and dynamic portfolio management, systems and methods for underwriting and portfolio management include an ecosystem including a platform, including processing devices, communication interfaces, runtime environments, and databases, where the databases are configured to store ecosystem data, where the ecosystem data includes data associated with a plurality of systems. A service layer is in communication with the platform, the service layer including containers executed in the runtime environment and configured to implement microservices, where each of the containers include: at least one microservice and a datastore device configured to store domain-specific data. An orchestrator is in communication with the service layer, the orchestrator to schedule execution of the microservices according to bounded contexts coordinated with composite application programming interfaces (API) interfacing with a microservice specific API.

In some implementations, a user interface for an application is displayed using a web browser instance on a client device. An input is received to present data on the user interface in a particular view. In response to the input, a first web worker thread corresponding to the web browser instance obtains data from a server, and executes first library routines to store the data in local storage at the client device. A second web worker thread, which corresponds to the web browser instance and the user interface, accesses the data from the local storage by using one or more second library routines, and processes the data to convert to a presentation format corresponding to the particular view. The second web worker thread stores the processed data in the local storage by using one or more third library routines, and provides the processed data for display on the user interface.

Methods and systems for unifying display of virtual resources are described herein. A virtual session between a client device and a server device may be established. During the virtual session, a user may request, via the client device, to access a uniform resource locator (URL) via a browser associated with the server device. The URL request may be redirected. For example, the client device may receive, from the server device, a request to access the URL via a different browser. The client device may determine another browser with which to access the URL, and the URL may be launched via the other browser. The client device may generate a unified display of the URL launched via the other browser and one or more other URLs.

A method includes, in a processor of a user device, deciding to preload a user application, which has one or more User Interface (UI) displays whose state is retained by the processor in a memory of the user device. At least part of the user application is preloaded, and a state of the preloaded user application is restored, in a background mode, to match the retained state of the one or more UI displays.

The disclosed embodiments relate to a system that facilitates developing applications in a component-based software development environment. This system provides an execution environment comprising instances of application components and a registry that maps names to instances of application components. Upon receiving a call to register a mapping between a name and an instance of an application component, the system updates the registry to include an entry for the mapping. Moreover, upon receiving a call to be notified about registry changes for a name, the system updates the registry to send a notification to a caller when a registry change occurs for the name.