Abstract: Systems and methods for activity-based device recommendations are disclosed. For example, historical usage data associated with a device may indicate that the device is likely to be associated with a given state at a given time. When the device is not in the anticipated state, a recommendation to transition the device state, for example, may be sent. Additionally, a determination of the activity state associated with the device, such as an active state, an asleep state, and/or an away state may be utilized to determine the recommendation to surface, to determine whether to send a recommendation, and when and/or how to send the recommendation.

Abstract: Systems and methods for usage-based device naming and grouping are disclosed. For example, trigger events that indicate when a device should be renamed, added to a device group, and/or added to a routine may be determined. Usage data representing usage of the device may be received and utilized to determine if a trigger event occurs. When a trigger event occurs, a recommendation for renaming, grouping, etc. may be determined and sent to a user device. Upon acceptance of the recommendation, the device may be renamed, grouped, and/or added to a routine.

Abstract: Systems and methods for usage-based device naming and grouping are disclosed. For example, trigger events that indicate when a device should be renamed, added to a device group, and/or added to a routine may be determined. Usage data representing usage of the device may be received and utilized to determine if a trigger event occurs. When a trigger event occurs, a recommendation for renaming, grouping, etc. may be determined and sent to a user device. Upon acceptance of the recommendation, the device may be renamed, grouped, and/or added to a routine.

Abstract: Systems and methods for usage-based device naming and grouping are disclosed. For example, trigger events that indicate when a device should be renamed, added to a device group, and/or added to a routine may be determined. Usage data representing usage of the device may be received and utilized to determine if a trigger event occurs. When a trigger event occurs, a recommendation for renaming, grouping, etc. may be determined and sent to a user device. Upon acceptance of the recommendation, the device may be renamed, grouped, and/or added to a routine.

Abstract: A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.

Abstract: A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.