Notification Synchronization via Device Activity Status
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The bring-your-own-device paradigm leads to notification clutter and security risks due to excessive notifications on multiple devices, with 'stale' notifications not being synchronized properly across devices, causing unnecessary clutter and potential data leaks.
Innovation Solution
A system that tailors notification posting based on device activity status, synchronizing notification actions across devices by defining active devices as those currently in use, and enabling or disabling notification capabilities and synchronization based on user activity, ensuring that notifications are only displayed on actively used devices and their states are updated accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If notifications are posted on all enrolled devices, then user accessibility to enterprise applications is improved, but notification clutter and security risks increase
Solution Approach 1:
The system applies different notification posting rules to different devices based on their activity status. Active devices receive and display notifications with full functionality, while inactive devices have notification posting disabled or restricted. This local differentiation resolves the contradiction by tailoring notification behavior to each device's current usage state rather than applying a uniform approach to all devices.
Solution Approach 2:
The system dynamically determines device activity status and adjusts notification posting capabilities in real-time. Devices transition between active and inactive states based on usage patterns, and notification behavior adapts accordingly. This dynamic approach ensures that notification clutter is prevented on inactive devices while maintaining accessibility on active devices.
2Ease of operation
If notifications are posted on all enrolled devices, then user accessibility to enterprise applications is improved, but security risks from confidential data exposure increase
Solution Approach 1:
The system applies enhanced security measures specifically to inactive devices while maintaining normal notification functionality on active devices. On inactive devices, notification posting is disabled, confidential data is not displayed, and biometric authentication is required for any data access. This localized security approach prevents data exposure on unused devices without impacting user accessibility on actively used devices.
Solution Approach 2:
The system proactively prevents security risks by disabling notification posting and data display on inactive devices before any potential data leak can occur. By identifying inactive devices and applying restrictive measures in advance, the system prevents confidential data exposure rather than reacting to security incidents after they occur.
3Productivity
If notification actions are synchronized across all devices, then user productivity is improved, but device complexity and synchronization overhead increase
Solution Approach 1:
The system applies notification synchronization selectively based on device activity status. When a user interacts with a notification on an active device, the action is synchronized to other active devices. Inactive devices are excluded from synchronization operations, reducing the complexity and overhead of maintaining notification state across the entire device fleet while preserving productivity benefits on actively used devices.
4Ease of operation
If notification posting is enabled on multiple devices, then user convenience is improved, but stale notifications create clutter and require duplicate actions
Solution Approach 1:
The system dynamically manages notification lifecycle across devices based on real-time activity status. When a notification is acted upon on any device, the system identifies which other devices are currently active and synchronizes the notification state only to those devices. Inactive devices automatically retain stale notifications without requiring manual cleanup, as they are excluded from receiving new notifications and are not targeted for state synchronization. This dynamic, activity-based approach maintains notification state consistency across active devices while preventing clutter on inactive devices.
Data Source
AI summary
Disclosed herein are examples of systems and methods for synchronizing notification actions across multiple enrolled devices. A management service can receive from a first client device metadata associated with a notification posted on the first client device. The management service can receive from the first client device an indication of an action performed with respect to the notification. The management service can determine whether to propagate a new notification state to a second client device based at least in part on a type of the action and a current notification state associated with the second client device. In response to determining to propagate the new notification state to the second client device, the management service can provide to the second client device a command to change the current notification state to the new notification state.