Selective Native App Notification via Compatibility Check

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current content serving technologies fail to effectively manage the display of native application alternatives to users, often resulting in unnecessary notifications and compatibility issues across different devices, without proper user control or verification of the native applications.

Innovation Solution

Incorporating a reference to the native application in the webpage code, allowing the browser or client device to determine whether to display a notification for the native application based on user settings, device compatibility, and application status, ensuring that notifications are only shown to users who can install and benefit from the native application, and verifying the application's legitimacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If notifications are displayed for all web applications with native application alternatives, then user awareness of native application options is improved, but user annoyance and notification spam increase

Engineering Contradiction:

Improveuser awareness of native application optionsVSAvoiduser annoyance and notification spam

Core Design Contradiction:

Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The notification display is made selective based on local device characteristics and user state. The system determines whether to display notifications by checking device compatibility, whether the user has previously interacted with the web application, and current user preferences. This localized quality control ensures notifications are shown only when relevant, reducing user annoyance while maintaining awareness.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The notification display behavior is made dynamic and adaptive. The system continuously monitors user interactions and device state, adjusting notification display in real-time. If a user has already installed or interacted with a native application, the system dynamically suppresses further notifications for that application, preventing spam while maintaining awareness for relevant cases.

Inventive Principle:

Principle #15Dynamics

2Productivity

If notifications are displayed without checking device compatibility, then notification volume increases, but compatibility issues and failed installations occur

Engineering Contradiction:

Improvenotification delivery volumeVSAvoidinstallation compatibility

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary compatibility checking before displaying notifications. It evaluates device characteristics such as operating system version, hardware capabilities, and installed applications to determine in advance whether a native application can be successfully installed. This preliminary action filters out incompatible devices before notification delivery, ensuring high reliability of installation while maintaining appropriate notification volume for compatible devices.

Inventive Principle:

Principle #10Preliminary action

3Object-affected harmful factors

If the system verifies native application legitimacy, then security against malicious applications is improved, but system complexity and verification time increase

Engineering Contradiction:

Improvesecurity against malicious applicationsVSAvoidverification system complexity

Core Design Contradiction:

Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The system introduces an intermediary verification layer that mediates between the web application and the native application installation. This intermediary component validates application legitimacy by checking digital signatures, publishing authority, and application metadata before allowing installation. The intermediary handles the complexity of verification centrally, simplifying the overall system architecture while maintaining strong security against malicious applications.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Object-affected harmful factors

If notifications are suppressed for already installed applications, then user annoyance is reduced, but user awareness of application updates is lost

Engineering Contradiction:

Improveuser annoyance from redundant notificationsVSAvoiduser awareness of application updates

Core Design Contradiction:

Object-affected harmful factorsVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms that monitor user interactions and application state. When a user installs a native application, the system receives feedback and suppresses further notifications for that application to reduce annoyance. However, the feedback loop also detects when updates are available and selectively re-activates notifications for updated versions, maintaining user awareness of important changes while avoiding redundant notifications for stable versions.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9195479B2Selective notification of native applications

Publication Date: 2015.11.24 GOOGLE LLC

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for providing selective notifications. In one aspect, a method includes receiving code for a web application, the code including a reference to a native application equivalent to the web application, and determining whether to display a notification regarding the native application equivalent to the web application, then selectively displaying the notification regarding the native application equivalent to the web application based on the determination.