Dynamic Application Skinning via Asset Package Replacement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online content delivery systems require a new request for content each time content is needed in an electronic application, leading to inefficiencies and unnecessary data transfer, especially when multiple alternative items of content are cached for rotation.

Innovation Solution

A method and system for skinning applications with interactive content by receiving an electronic package of assets from a content provider, replacing placeholders in the application with content items from the package, and updating content based on events identified within the application, allowing for dynamic and efficient content management without re-downloading the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a new request for content is made for each field in an electronic application, then content can be dynamically updated, but data transfer overhead and system inefficiency increase

Engineering Contradiction:
Improvecontent update capabilityVSAvoiddata transfer overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system performs preliminary action by receiving and caching multiple alternative items of content in advance before they are needed. Content is pre-fetched and stored in memory, so when a field needs to be updated, the content is already available locally without requiring a new request. This resolves the contradiction by maintaining adaptability through pre-cached alternatives while eliminating the energy loss of repeated data transfer requests.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple alternative items of content are cached for rotation, then content variety is improved, but memory usage increases

Engineering Contradiction:
Improvecontent varietyVSAvoidmemory usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system applies universality by creating a single electronic package of assets that can serve multiple fields simultaneously. Instead of caching separate content sets for each field, one universal package contains alternative items that can be rotated across multiple fields, providing content variety while sharing the same memory resources. This reduces overall memory usage compared to maintaining separate cached content for each field.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If content is updated responsive to events in the application, then user experience is enhanced, but system complexity increases

Engineering Contradiction:
Improveuser experienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically monitoring application events and triggering content updates without requiring complex external control mechanisms. The electronic package of assets contains content alternatives that can be automatically selected and applied based on event types, allowing the system to enhance user experience through event-responsive updates while minimizing the complexity of update management through automated self-service logic.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9727316B2Systems and methods for skinning an application with interactive content
Publication Date: 2017.08.08 GOOGLE LLC
  • US9727316B2 patent drawing
  • US9727316B2 patent drawing
  • US9727316B2 patent drawing

AI summary

In one implementation, an electronic package of assets substantially complying with a standard is received from a content provider. Placeholders in an application referring to items of content defined by the standard are replaced with items of content from the package of assets. In another implementation, an electronic package of assets substantially complying with a standard is received from a content provider. A publisher is identified, the package of assets is provided to the publisher, and an application incorporating items from the package of assets is received. In another implementation, a package of assets substantially complying with a standard is prepared, an application is received from a publisher, and a version of the application is generated, replacing references in the application to items defined in a standard with items of content from the package of assets.