Abstract:
A multi-selection system allows selection of multiple displayed items in a GUI, and processes an underlying data set based on the selection. Users may utilize swipes or concurrent point interactions with the GUI to co-select items. The system identifies actions to perform for selected items based on selection criteria associated with the selected items, or mapping data that maps the selected items to actions. The system automatically identifies grouping criteria for data returned from performed actions and displays resulting groups for further user selection. The system provides suggestive visual highlights that identify commonly co-selected items in the interface. The system collects instrumentation items, for historical usage data, that record aspects of users' interactions with the system. As such, the system may identify, from the historical usage data, sets of commonly co-selected items, mappings between combinations of items and one or more actions, productive arrangements of items displayed in GUIs, etc.
Abstract:
A multi-selection system allows selection of multiple displayed items in a GUI, and processes an underlying data set based on the selection. Users may utilize swipes or concurrent point interactions with the GUI to co-select items. The system identifies actions to perform for selected items based on selection criteria associated with the selected items, or mapping data that maps the selected items to actions. The system automatically identifies grouping criteria for data returned from performed actions and displays resulting groups for further user selection. The system provides suggestive visual highlights that identify commonly co-selected items in the interface. The system collects instrumentation items, for historical usage data, that record aspects of users' interactions with the system. As such, the system may identify, from the historical usage data, sets of commonly co-selected items, mappings between combinations of items and one or more actions, productive arrangements of items displayed in GUIs, etc.
Abstract:
A multi-selection system allows selection of multiple displayed items in a GUI, and processes an underlying data set based on the selection. Users may utilize swipes or concurrent point interactions with the GUI to co-select items. The system identifies actions to perform for selected items based on selection criteria associated with the selected items, or mapping data that maps the selected items to actions. The system automatically identifies grouping criteria for data returned from performed actions and displays resulting groups for further user selection. The system provides suggestive visual highlights that identify commonly co-selected items in the interface. The system collects instrumentation items, for historical usage data, that record aspects of users' interactions with the system. As such, the system may identify, from the historical usage data, sets of commonly co-selected items, mappings between combinations of items and one or more actions, productive arrangements of items displayed in GUIs, etc.
Abstract:
A multi-selection system allows selection of multiple displayed items in a GUI, and processes an underlying data set based on the selection. Users may utilize swipes or concurrent point interactions with the GUI to co-select items. The system identifies actions to perform for selected items based on selection criteria associated with the selected items, or mapping data that maps the selected items to actions. The system automatically identifies grouping criteria for data returned from performed actions and displays resulting groups for further user selection. The system provides suggestive visual highlights that identify commonly co-selected items in the interface. The system collects instrumentation items, for historical usage data, that record aspects of users' interactions with the system. As such, the system may identify, from the historical usage data, sets of commonly co-selected items, mappings between combinations of items and one or more actions, productive arrangements of items displayed in GUIs, etc.
Abstract:
Techniques for detecting and addressing performance issues related to a mobile application are provided. Examples of performance issues include a backend service (to which the mobile application is configured to transmit requests) becoming unavailable or overloaded, a third-party service that the mobile application relies on for data pertaining to the backend service becoming unavailable, and security vulnerabilities or code irregularities in the code of the mobile application. A fallback service that is separate from the backend service detects the performance issues and sends fallback data to the mobile application. The fallback data may cause the mobile application to operate in an offline mode, where the mobile application requests locally stored data instead of transmitting data requests to the backend service. The fallback data may reference page views that the mobile application downloads and displays instead of other page views that are based on data from the backend service.
Abstract:
An operator of a first device is verified using biometric data detected by the first device. Responsive to successfully completing the verification, the first device data in a decrypted form that is displayed in an encrypted form on a second device.
Abstract:
A method and system for adaptive event scheduling are provided. A first start time and a first duration are automatically selected for a first calendar event. The first calendar event is for a first learning activity of the course. Insertion of the first calendar event is caused, at the first start time and with the first duration, into an electronic calendar associated with a user participating in a course. Behavior of the user relative to performance of the first learning activity is monitored. Based at least in part on the behavior, a second start time and a second duration are automatically selected for a second calendar event. The second calendar event is for a second learning activity of the course. Insertion of the second calendar event is caused, at the second start time and with the second duration, into the electronic calendar.
Abstract:
At least one pattern associated with a device is identified. Based on the pattern, a time is selected to synchronize data stored on the device with data stored on another device. A synchronization operation is performed at the selected time.
Abstract:
A multi-selection system allows selection of multiple displayed items in a GUI, and processes an underlying data set based on the selection. Users may utilize swipes or concurrent point interactions with the GUI to co-select items. The system identifies actions to perform for selected items based on selection criteria associated with the selected items, or mapping data that maps the selected items to actions. The system automatically identifies grouping criteria for data returned from performed actions and displays resulting groups for further user selection. The system provides suggestive visual highlights that identify commonly co-selected items in the interface. The system collects instrumentation items, for historical usage data, that record aspects of users' interactions with the system. As such, the system may identify, from the historical usage data, sets of commonly co-selected items, mappings between combinations of items and one or more actions, productive arrangements of items displayed in GUIs, etc.
Abstract:
Techniques for detecting and addressing performance issues related to a mobile application are provided. Examples of performance issues include a backend service (to which the mobile application is configured to transmit requests) becoming unavailable or overloaded, a third-party service that the mobile application relies on for data pertaining to the backend service becoming unavailable, and security vulnerabilities or code irregularities in the code of the mobile application. A fallback service that is separate from the backend service detects the performance issues and sends fallback data to the mobile application. The fallback data may cause the mobile application to operate in an offline mode, where the mobile application requests locally stored data instead of transmitting data requests to the backend service. The fallback data may reference page views that the mobile application downloads and displays instead of other page views that are based on data from the backend service.