Abstract: In a first device including a processor and a memory in communication with the processor, the memory includes executable instructions that, when executed by the processor, cause the processor to control the first device to perform functions of receiving, from a second device via a signal connection, a request to project visual content from the second device, the first device being in a locked state to restrict access to the first device that requires valid authentication to transition from the locked state to an unlocked state; determining that the second device has a permission to project the visual content to the first device; receiving, from the second device via the signal connection, data for projecting the visual content to the first device; and based on the received data, displaying, on a display, the visual content.

Abstract: In a first device including a processor and a memory in communication with the processor, the memory includes executable instructions that, when executed by the processor, cause the processor to control the first device to perform functions of receiving, from a second device via a signal connection, a request to project visual content from the second device, the first device being in a locked state to restrict access to the first device that requires valid authentication to transition from the locked state to an unlocked state; determining that the second device has a permission to project the visual content to the first device; receiving, from the second device via the signal connection, data for projecting the visual content to the first device; and based on the received data, displaying, on a display, the visual content.

Abstract: Techniques for projection via a device are described. According to various implementations, techniques described herein enable a locked host device to output data projected from another device while the host device remains in a locked state. In at least some implementations, device context for a host device (locked or unlocked) can be considered in determining whether to broadcast availability to receive projected content.

Abstract: Techniques for projection via a device are described. According to various implementations, techniques described herein enable a locked host device to output data projected from another device while the host device remains in a locked state. In at least some implementations, device context for a host device (locked or unlocked) can be considered in determining whether to broadcast availability to receive projected content.

Abstract: In some examples, input received from an input device, such as a keyboard, is modified by a component associated with an operating system before the input is delivered to an application. For instance, a component associated with the operating system may become registered for modifying input. In some situations, the input is modified based at least in part on metadata associated with the input device. For example, a location of a fingertip on a touch-sensitive display may be used to modify the input before delivery to an application.

Abstract: Techniques for projection via a device are described. According to various implementations, techniques described herein enable a locked host device to output data projected from another device while the host device remains in a locked state. In at least some implementations, device context for a host device (locked or unlocked) can be considered in determining whether to broadcast availability to receive projected content.

Abstract: In example embodiments, a machine receives, from a computing device of a health professional, a treatment plan for a patient. The machine receives, from a plurality of devices associated with the patient, activity data related to the patient. The machine determines that the activity data is related to compliance with the treatment plan. The machine provides, in response to determining that the activity data is related to compliance with the treatment plan, the activity data to the computing device of the health professional.

Abstract: In example embodiments, a machine receives, at a server and from a computing device of a health professional, a treatment plan for a patient, the treatment plan comprising a plurality of tasks and a physiological goal. The machine receives, from a plurality of devices associated with the patient, activity data and physiological data related to the patient. The machine determines, based on the activity data and the physiological data, the patient's compliance with one or more tasks in the treatment plan. The machine updates the treatment plan based on the patient's compliance with the one or more tasks, the physiological goal, and a model based on an information tuple about the patient.

Abstract: In example embodiments, a machine receives, from a first computing device of a first health professional, a first treatment plan for a patient. The machine receives, from a second computing device of a second health professional, a second treatment plan for the patient. The machine receives, from a plurality of devices associated with the patient, activity data related to the patient. The machine stores, in a data repository, the first treatment plan, the second treatment plan, and the activity data.

Abstract: In example embodiments, a machine receives a medical record of a patient. The machine receives, from devices associated with the patient, activity data and physiological data related to the patient. The machine normalizes the activity data and the physiological data. The machine determines adherence to one or more tasks in a treatment plan based on the medical record, the activity data, and the physiological data by comparing the medical record, the activity data or the physiological data with one or more threshold values, the one or more threshold values residing in a medical data repository or being provided from a computing device of a health professional. The machine selects, for provision to a health professional, a portion of the medical record, a portion of the activity data, and a portion of the physiological data based on a specification provided by the health professional and permission provided by the patient.

Abstract: Techniques for projection via a device are described. According to various implementations, techniques described herein enable a locked host device to output data projected from another device while the host device remains in a locked state. In at least some implementations, device context for a host device (locked or unlocked) can be considered in determining whether to broadcast availability to receive projected content.

Abstract: Touch-input support for an external touch-capable display device is described. A computing device (e.g., a smartphone) is configured to form a connection with an external touch-capable display device that is separate from the computing device. The computing device controls the display of information on the touch-capable display device. A user of the computing device can interact with the external touch-capable display device, such as by touching the screen of the touch-capable display device to select items, perform gestures, or type on the on-screen keyboard. When the user provides touch-input to the external touch-capable display device, the computing device receives an indication of the touch-input via the wired or wireless connection. The computing device then modifies the display of information on the touch-capable display device based on the touch-input.

Abstract: In some examples, input received from an input device, such as a keyboard, is modified by a component associated with an operating system before the input is delivered to an application. For instance, a component associated with the operating system may become registered for modifying input. In some situations, the input is modified based at least in part on metadata associated with the input device. For example, a location of a fingertip on a touch-sensitive display may be used to modify the input before delivery to an application.

Abstract: Disclosed are techniques and systems for obtaining contextual information at least in part from a keyboard, to improve typing efficiencies and user experience. The contextual information may include keyboard attributes, typing metadata, user actions, and the like. The keyboard may be configured to detect an input event at the keyboard. A human interface device (HID) stack is configured to receive the contextual information, and a keyboard manager is configured to determine an output based at least in part on the input event and the contextual information. The output may be a most probable function (non-text-based output), or character or word (text-based output) that can be suggested or used to auto-correct application data. In some embodiments, the user action received in the contextual information may be translated to a gesture to manipulate application data.

Abstract: Embodiments include processes, systems, and devices for brokering application access to capabilities, such as device capabilities. An access broker receives requests from applications to access capabilities. The access broker determines whether to grant access based at least in part on whether the application manifest declares the capability. The access broker also may cause a user interface element to be displayed requesting user consent to the access request. Also, an in-application user interface element is provided that displays capability access settings for a particular application. The in-application user interface element includes selectable options for changing those settings. Changes in those settings via the user interface update the settings in the access broker.