Abstract: Graph capabilities are embedded as a service (e.g., a software as a service (SAAS)) into relational databases or other databases so that graph analytics can be realized and relationships can be analyzed. A seamless graph analytics experience, using a graph analytics system, is provided to a database platform. Advantages include security and advance graph analytics can be run on data in database platforms (e.g., relational databases, kv-stores, etc.) The database platform console can be used to instruct the graph analytics to be performed on the data in the database platform. The insights and results from the graph analytics may be stored in the database platform as tables and can be joined with other data of the database platform and/or used in machine learning. A user of the database platform does not have to leave that environment to perform graph analytics on the data of the database platform.

Abstract: A method for rule-based composition of user interfaces. A machine-learned rule repository is established based on previously observed combinations of UI states, UI features, and user features. A classifier classifies users into segments. Each segment includes users for which a combination of user features and UI states are defined. A first machine learning model (MLM) estimates a user segment-content preference including preferred UI content. A second MLM estimates a seen content-seen content similarity UI content preferences estimated according to prior UI content a user has seen. Based on the UI state and based on the user ID, rule-based recipes are obtained. Each rule-based recipe specifies a corresponding UI content suitable for an interaction between the user and the interface. A selected rule-based recipe is selected from the rule-based recipes. Specific UI content specified by the selected rule-based recipe is obtained, and the interface is updated with the specific UI content.

Abstract: A method for rule-based composition of user interfaces involves obtaining a user identity (ID) of a user accessing an application using a user interface and obtaining a user interface (UI) state of the user interface. Based on the UI state and based on the user ID, a plurality of rule-based recipes are obtained. Each rule-based recipe specifies a UI content suitable for an interaction between the user and the user interface. The method further includes ranking each of the rule-based recipes of the plurality of rule-based recipes based on a likeliness that the rule-based recipe is suitable, given the UI state and the user ID, identifying, from the ranked plurality of rule-based recipes, a highest-ranked rule-based recipe, obtaining the UI content specified by the highest-ranked rule-based recipe, and updating the user interface with the UI content.

Abstract: This disclosure relates to facilitating communication between widgets of cross-platform applications. An exemplary system includes computing components configured to execute an application shell. The system is configured to cause the application shell to do the following. The application shell instantiates a cross-platform application comprising a plurality of application widgets. The application shell then determines that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The application shell then receives a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The application shell then receives a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: This disclosure relates to facilitating communication between widgets of cross-platform applications. An exemplary system includes computing components configured to execute an application shell. The system is configured to cause the application shell to do the following. The application shell instantiates a cross-platform application comprising a plurality of application widgets. The application shell then determines that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The application shell then receives a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The application shell then receives a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget.

Abstract: Certain aspects of the present disclosure provide techniques for facilitating communication between widgets of cross-platform applications. An exemplary system is configured to instantiate a cross-platform application comprising a plurality of application widgets. The system is further configured to determine that a first application widget of the plurality of application widgets executes instructions through an execution container of the cross-platform application. The system is further configured to receive a request comprising criteria from the first application widget, wherein the criteria specify an application widget to listen for communications from. The system is further configured to receive a communication from the second application widget and determines that the communication matches the criteria of the request by the first application widget. The system is further configured to transmit to the first application widget an update containing data from the communication.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of user interface components. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes customizing one or more widgets by selecting one or more user interface components to include in the one or more widgets based on the user intent. The method further includes generating a custom user interface definition comprising the one or more widgets. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: This disclosure relates to cross-platform applications that include native and non-native components on mobile devices. An exemplary method generally includes receiving a first workflow step definition including a first set of widgets to be loaded into an application shell. A mobile shell identifies a type of each widget in the first set of widgets (e.g., native or platform-agnostic) and loads each widget into the mobile shell based on the widget type. For a platform-agnostic widget, the mobile shell creates a platform-agnostic widget proxy service, which provides a runtime environment. The platform-agnostic widget may be loaded into the platform-agnostic widget proxy service and executes in the runtime provided thereby.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: This disclosure relates to customizing deployment of an application to a user interface of a client device. An exemplary method generally includes training a model based on historical context information of a plurality of users by identifying correlations between the historical context information and a plurality of widgets and storing the correlations in the model. The method further includes receiving context information from the client device. The method further includes determining a user intent based on the context information using the model. The method further includes selecting one or more widgets to include in a custom user interface definition based, at least in part, on the user intent. The method further includes transmitting, to the user interface of the client device, the custom user interface definition.

Abstract: This disclosure relates to cross-platform applications that include native and non-native components on mobile devices. An exemplary method generally includes receiving a first workflow step definition including a first set of widgets to be loaded into an application shell. A mobile shell identifies a type of each widget in the first set of widgets (e.g., native or platform-agnostic) and loads each widget into the mobile shell based on the widget type. For a platform-agnostic widget, the mobile shell creates a platform-agnostic widget proxy service, which provides a runtime environment. The platform-agnostic widget may be loaded into the platform-agnostic widget proxy service and executes in the runtime provided thereby.

Abstract: Systems and methods for using distributed Universal Serial Bus (USB) host drivers are disclosed. In one aspect, USB packet processing that was historically done on an application processor is moved to a distributed USB driver running in parallel on a low-power processor such as a digital signal processor (DSP). While a DSP is particularly contemplated, other processors may also be used. Further, a communication path is provided from the low-power processor to USB hardware that bypasses the application processor. Bypassing the application processor in this fashion allows the application processor to remain in a sleep mode for longer periods of time instead of processing digital data received from the low-power processor or the USB hardware. Further, by bypassing the application processor, latency is reduced, which improves the listener experience.

Abstract: This disclosure relates to cross-platform applications that include native and non-native components on mobile devices. An exemplary method generally includes receiving a first workflow step definition including a first set of widgets to be loaded into an application shell. A mobile shell identifies a type of each widget in the first set of widgets (e.g., native or platform-agnostic) and loads each widget into the mobile shell based on the widget type. For a platform-agnostic widget, the mobile shell creates a platform-agnostic widget proxy service, which provides a runtime environment. The platform-agnostic widget may be loaded into the platform-agnostic widget proxy service and executes in the runtime provided thereby.

Abstract: Systems and method for inferring polling rates for Universal Serial Bus (USB) endpoints include a driver in an audio device that measures a feedback polling interval from a host device for a plurality of periods. Based on observed periods, the audio device infers a polling period by the host device and adjusts when a feedback signal is sent to conform to the inferred polling period. By adjusting the audio device based on behavior of the operating system, the audio device may work with multiple operating systems, providing greater flexibility for an end user and also reducing the likelihood of artifacts degrading the user experience.

Abstract: Apparatuses, methods, and systems for enabling higher current charging of Universal Serial Bus (USB) Specification Revision 2.0 (USB 2.0) portable electronic devices from USB 3.x hosts are disclosed. In one aspect, a USB 2.0 controller is provided in a USB 2.0 portable device. A USB 3.x controller is provided in a USB 3.x host. The USB 2.0 controller is configured to draw a higher charging current than specified in USB 2.0 for the USB 2.0 portable device over a USB 2.0 cable. In order to draw the higher charging current without violating USB 2.0, the USB 2.0 controller is configured to use one or more reserved elements in an existing USB 2.0 descriptor(s) or bitmap(s) to indicate a higher charging current request from the USB 2.0 controller.

Abstract: Systems and methods for using distributed Universal Serial Bus (USB) host drivers are disclosed. In one aspect, USB packet processing that was historically done on an application processor is moved to a distributed USB driver running in parallel on a low-power processor such as a digital signal processor (DSP). While a DSP is particularly contemplated, other processors may also be used. Further, a communication path is provided from the low-power processor to USB hardware that bypasses the application processor. Bypassing the application processor in this fashion allows the application processor to remain in a sleep mode for longer periods of time instead of processing digital data received from the low-power processor or the USB hardware. Further, by bypassing the application processor, latency is reduced, which improves the listener experience.

Abstract: A method of triggering a desired operating mode in a universal serial bus (USB)-compatible client device is provided. A USB-compatible client device detects that it has been coupled to a USB-compatible host device via a USB bus. The USB-compatible client device attempts to pull a data line of the USB bus high. The USB-compatible client device then ascertains that the data line remains pulled low, thereby indicating that the USB-compatible client device should enter a first mode of operation. The USB-compatible client device operates according to the first mode of operation.

Abstract: Electronic devices are adapted to facilitate detection of a type of USB charger to which an electronic device is connected. According to one example, an electronic device can apply a current source to a data line of a USB plug coupled to a USB port. A determination can be made whether the data line has gone to a LOW state or remained at a HIGH state after a predetermined period of time. If the data line has gone to a LOW state, the USB port may be identified as a downstream port, such as a standard downstream port (SDP) or a charging downstream port (CDP). If the data line has remained at the HIGH state, the USB port may be identified as a dedicated charging port (DCP), no matter if it is compliant or non-compliant with the BC 1.2 spec. Other aspects, embodiments, and features are also included.

Abstract: Apparatuses and methods to distinguish proprietary, non-floating and floating chargers for regulating charging current are disclosed. In one aspect, a charger detection circuit is provided in a portable electronic device. The charger detection circuit is configured to detect whether a connected Universal Serial Bus (USB) charger is compliant with a USB battery charging specification. If the connected USB charger is non-compliant with the USB battery charging specification, the charger detection circuit is configured to further detect if the non-complaint USB charger is a non-compliant floating USB charger or a non-compliant proprietary USB charger. If the connected USB charger is determined to be a non-compliant proprietary USB charger, the portable electronic device can be configured to draw up to a maximum charging current according to the USB battery charging specification.