Customizable Notification System for Software Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users are often unaware of the nature and value of software updates, leading to disengagement due to non-specific and frequency-irrelevant notifications, which fail to align with their needs and expectations.

Innovation Solution

A customizable notification system that provides users with detailed information about updates, allowing control over who sees the notification, its duration, and target audience, using a backend service to dynamically manage notification behavior and content, ensuring users are informed and invested in the update process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If generic notification messages are used to notify users of updates, then the notification system is simple to implement, but users are unaware of the nature and value of updates leading to disengagement

Engineering Contradiction:
Improveinformation about update nature and valueVSAvoidnotification system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The notification system is segmented into multiple components: a notification generator that creates base notifications, a customization module that adds user-specific information about update nature and value, and a delivery system that manages timing and targeting. This segmentation allows detailed information to be provided without creating a monolithic complex system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-generating notification templates with placeholders for update information, and pre-configuring delivery rules based on user profiles and device states. This preliminary preparation reduces the complexity of real-time notification customization while still providing detailed update information.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If notifications are provided with fixed frequency and timing, then the notification system is easy to manage, but the frequency bears no relation to user needs and expectations

Engineering Contradiction:
Improvenotification frequency adaptation to user needsVSAvoidnotification management ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The notification system transitions from static fixed-frequency delivery to dynamic adaptive delivery. The system continuously monitors user engagement patterns, device usage states, and update priorities to dynamically adjust notification timing and frequency. This dynamic adaptation increases versatility in meeting user needs while maintaining automated management through algorithmic decision-making.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback loops where user responses to notifications (such as engagement, dismissal, or installation actions) are fed back into the notification management system. This feedback informs future notification timing and frequency adjustments, allowing the system to adapt to user needs while maintaining ease of operation through automated learning and adjustment.

Inventive Principle:
Principle #23Feedback

3Reliability

If detailed update information is provided in notifications, then user engagement and awareness increase, but the notification content and delivery must be highly customizable

Engineering Contradiction:
Improveuser engagement and installation rateVSAvoidnotification customization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The notification system applies local quality by providing different levels of detail and customization to different user segments based on their specific needs, device types, and engagement patterns. Rather than uniformly customizing all notifications, the system tailors information depth and delivery timing to local user contexts, increasing engagement while managing complexity through targeted customization.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system manages customization complexity by parameterizing notification templates with configurable variables for information depth, timing, and targeting. These parameters can be adjusted independently and systematically, allowing detailed update information to be provided with controlled customization through parameter management rather than content creation for each notification.

Inventive Principle:
Principle #35Parameter changes

4Loss of information

If notifications are displayed frequently to ensure users see update information, then user awareness increases, but users may be frustrated with overly-intrusive notifications

Engineering Contradiction:
Improveuser awareness of updatesVSAvoiduser frustration from intrusive notifications
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The notification system implements periodic action by scheduling notifications at optimal intervals rather than continuously or too frequently. The system determines appropriate periodic intervals based on update importance, user engagement patterns, and device usage cycles, ensuring users receive update information awareness while avoiding frustration from overly-intrusive frequent notifications.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS8266612B2Dynamic, customizable and configurable notification mechanism
Publication Date: 2012.09.11 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8266612B2 patent drawing
  • US8266612B2 patent drawing
  • US8266612B2 patent drawing

AI summary

Provided are arrangements for delivering customized application or update notifications corresponding to a software application so that a user may be informed of the value of the application or update. In addition, the notifications may be rendered by a configurable notification mechanism so that the behavior of the notification, i.e., when and how often it is displayed, to what users and in what conditions, and the like, is also configurable. In this way, users become more invested in the application or update, are more likely to install the same, and become more aware of what changes to expect following installation.