G06F2209/545

GENERATING A DYNAMIC DEPENDENT CLIENT DEVICE ACTIVITY DASHBOARD AND MANAGING CONTACT-CONTROL PRIVILEGES VIA MANAGING CLIENT DEVICE INTERFACES

The present disclosure relates to systems, non-transitory computer-readable media, and methods for dynamically providing a activity dashboard for display within a graphical user interface. In particular, the disclosed systems can intelligently display, within the activity dashboard, insights of digital activity within an application of a child account. For example, the disclosed systems can monitor digital activity associated with recent contacts and groups, contact updates, and digital media items exchanged in messaging chat threads. In turn, the disclosed system can selectively surface one or more portions (and/or indications) of the monitored digital activity in the activity dashboard along with corresponding actionable options available for user selection. In response to user interaction with the actionable options corresponding to the selectively surfaced digital activity, the disclosed systems can intuitively modify the child account to regulate viewable content and digital communications with third-party child accounts.

Proxy Gesture Recognizer
20230244317 · 2023-08-03 ·

An electronic device displays one or more views. A first view includes a plurality of gesture recognizers. The plurality of gesture recognizers in the first view includes one or more proxy gesture recognizers and one or more non-proxy gesture recognizers. Each gesture recognizer indicates one of a plurality of predefined states. A first proxy gesture recognizer in the first view indicates a state that corresponds to a state of a respective non-proxy gesture recognizer that is not in the first view. The device delivers a respective sub-event to the respective non-proxy gesture recognizer that is not in the first view and at least a subset of the one or more non-proxy gesture recognizers in the first view. The device processes the respective sub-event in accordance with states of the first proxy gesture recognizer and at least the subset of the one or more non-proxy gesture recognizers in the first view.

LOCK SCREEN DISPLAY PROCESSING METHOD, TERMINAL AND STORAGE MEDIUM
20230244503 · 2023-08-03 ·

Provided are a lock screen display processing method, a terminal, and a storage medium. The method includes: in a case where a screen display space of a current lock screen interface is detected to be insufficient, obtaining a message source category corresponding to a received notification message; and according to the message source category, displaying the notification message in a drawer layout arrangement.

Auto-grouping of application windows

Described herein are techniques for automatically forming groups of application windows. The techniques may be performed with a computing device executing a windowing system, the windowing system having a user interface element that can be interacted with by a user to manage applications executing on the computing device. Each application may correspond to a separate process and application window. It may be determined that an operation has occurred that will evict the application windows of target applications from the display, and in response an application group may be automatically formed. The application group may have indicia of the evicted target applications. The application group may be provided to the user interface element, and when the user interface element is interacted with by the user the user interface element displays user-selectable graphic application indicators for both the application group and applications other than the target applications.

Declarative and reactive data layer for component-based user interfaces

Each of a plurality of wire web components predicted to be included in a graphical user interface (GUI) for presentation at a client machine. Each data object instance may be associated with a respective data object instance identifier and a respective one or more data object fields. A wire web component graph that includes a plurality of nodes may be constructed. A node may correspond to a wire web component, a data object field, or an application procedure interface (API). One or more of the data values may be retrieved from the respective APIs based on the wire web component graph. A GUI message including the retrieved data values and the wire web component graph may be transmitted to the client machine.

Application-specific graphical element detection
11232170 · 2022-01-25 · ·

Graphical element detection using a combined series and delayed parallel execution unified target technique that potentially uses a plurality of graphical element detection techniques, performs default user interface (UI) element detection technique configuration at the application and/or UI type level, or both, is disclosed. The unified target merges multiple techniques of identifying and automating UI elements into a single cohesive approach. A unified target descriptor chains together multiple types of UI descriptors in series, uses them in parallel, or uses at least one technique first for a period of time and then runs at least one other technique in parallel or alternatively if the first technique does not find a match within the time period.

AUTOMATED TASK MANAGEMENT TECHNIQUES

A system has a processor and a memory accessible by the processor and storing instructions, that when executed by the processor, cause the processor to generate a graphical user interface (GUI) for display on a display device. The GUI may include a job management dashboard that has multiple graphical icons that are representative of respective jobs associated with a client instance. The processor may receive one or more user inputs indicative of a selection of a particular graphical icon in the job management dashboard and transmit an update to GUI to the display device. The updated GUI may include a job overview window associated with a particular job, and the job overview window may display a graph of multiple run times associated with the particular job over a period of time.

Interactive display overlay systems and related methods
11182067 · 2021-11-23 · ·

In various embodiments, an interactive display overlay system is configured to serve as a gatekeeper for detected inputs on an interactive display screen (e.g., such as an interactive whiteboard or touch screen display) that is displaying a transparent overlay layer over an underlying software application. In various embodiments, the system is configured to detect an input at a particular location on the interactive display screen and determine whether there is a widget at that particular location on the transparent overlay layer before passing the input on to the underlying software application. In particular embodiments, the system is configured to modify inputs detected at the overlay layer that are proximate to a widget to an edge of the widget prior to passing on modified input data to the underlying software application.

Declarative and reactive data layer for component-based user interfaces

A wire web component may be included in a graphical user interface (GUI) being presented on a display device. The wire web component may include one or more data fields that are each associated with a respective data value. A designated node representing the designated wire web component may be removed from a wire web component graph that includes a plurality of nodes. Each of the data fields may be associated with a respective API in the wire web component graph. A document object model (DOM) tree stored in memory may be updated to remove the designated wire web component. The GUI presented on the display device may be updated based on the updated DOM tree.

COMPUTER-BASED SYSTEMS OF MICROSERVICE ORCHESTRATION BASED ON BOUNDED CONTEXTS AND METHODS OF USE THEREOF

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.