Notification Extensions for Preprocessing and Presenting Content

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing notification systems on computing devices require users to invoke separate applications to view additional content related to notifications, leading to increased memory usage and an inconvenient user experience, especially for quick interactions.

Innovation Solution

Implementing notification extensions that allow applications to preprocess and present notification content through service and content extensions, enabling customized processing and presentation without the need to invoke a separate application, thereby reducing overhead and enhancing user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a separate application is invoked to view additional notification content, then the user can access detailed content, but memory usage increases and user experience deteriorates

Engineering Contradiction:

Improvenotification content accessibilityVSAvoiduser experience

Core Design Contradiction:

Loss of informationVSEase of operation

Solution Approach 1:

The patent merges the notification viewing functionality directly into the notification interface by implementing a notification reader application. This allows users to view detailed notification content, interact with rich media, and perform actions without leaving the notification screen or invoking separate applications, thus maintaining memory efficiency while improving user experience.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The notification reader application serves as an intermediary component that bridges the notification system and detailed content viewing. It handles the preprocessing and presentation of notification content within the notification interface, acting as a mediator that eliminates the need to invoke full applications while still providing comprehensive content access.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Loss of information

If a separate application is invoked to view notification content, then complete content access is enabled, but memory resources are consumed

Engineering Contradiction:

Improvenotification content completenessVSAvoidmemory usage

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The notification reader application combines multiple functionalities (content viewing, rich media playback, interaction) into a single lightweight component that operates within the notification process, eliminating the need to load full applications into memory while maintaining complete content accessibility.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The notification reader application performs self-service by preprocessing and presenting notification content within the notification interface itself. It handles content rendering, media playback, and user interactions autonomously without requiring external application resources, thus minimizing memory consumption.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If notification content is viewed in a separate application, then full functionality is available, but the user experience becomes inconvenient

Engineering Contradiction:

Improvenotification functionalityVSAvoiduser convenience

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The notification reader application merges notification viewing, rich media playback, and interaction capabilities into a unified interface that users access directly from the notification screen. This integration maintains full functionality while eliminating the need to switch applications, significantly improving user convenience.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The notification reader application performs preliminary actions by preprocessing notification content and preparing it for display within the notification interface. This includes loading and rendering rich media, organizing content structure, and setting up interaction handlers before the user even views the notification, enabling immediate interaction without application invocation delays.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10693986B2Notification extensions for applications

Publication Date: 2020.06.23 APPLE INC

AI summary

In some implementations, a computing device can use notification extensions for applications to preprocess a notification received by the computing device and present content associated with a notification. For example, applications installed on the computing device can provide a service extension for preprocessing the notification. When a notification associated with the application is received, the notification system on the computing device can invoke the service extension for the application to preprocess the notification (e.g., to download additional content, encrypt/decrypt notification data, etc.). Applications can provide content extensions to present notification content. For example, a content extension associated with the application can be invoked by the notification system to present media content (or other content) associated with a received notification in an application specific manner.