Mobile App Resource Versioning for Visualization Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile applications often experience delays and crashes due to out-of-date versions, as users are prompted to update before they can use the latest features, leading to suboptimal functionality.

Innovation Solution

A system where a mobile device packages multiple versions of application resources, allowing it to use a compatible version for immediate functionality while downloading the latest version in the background, ensuring faster data visualization without waiting for the complete update.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the application waits for the latest version of application resources to be downloaded before generating visualizations, then the data visualization will use the most up-to-date resources, but the user experiences delays and cannot use the application features immediately

Engineering Contradiction:
Improveversion compatibilityVSAvoidupdate delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The application performs version checking and resource retrieval in advance before the user actually needs to use the visualization features. The system proactively determines whether the latest version of application resources is available and prepares it for use, rather than waiting until the user triggers a visualization request. This preliminary action eliminates the perceived delay for users.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application separates the version checking and resource retrieval process into distinct phases that occur independently of the user's visualization requests. The system segments the update mechanism from the core functionality, allowing the application to check for and retrieve resources in the background while the user can immediately use existing functionality.

Inventive Principle:
Principle #1Segmentation

2Reliability

If the application uses the latest version of application resources immediately, then the functionality will be most reliable and up-to-date, but the application size and download requirements increase

Engineering Contradiction:
Improveapplication functionalityVSAvoidapplication resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The application selectively retrieves and stores only the specific versions of application resources that are needed for particular visualization types or features. Rather than downloading all possible resource versions, the system determines the appropriate version based on the specific visualization request and retrieves only that portion, optimizing the balance between having up-to-date resources and minimizing download size.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The application dynamically adjusts which version of application resources to use based on the specific visualization parameters and requirements. The system can switch between different resource versions depending on the data type, visualization complexity, and device capabilities, rather than always using the latest version for all scenarios.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the application checks for the latest version of application resources before each visualization, then the resources will always be up-to-date, but the processing time and complexity increase

Engineering Contradiction:
Improveresource version currencyVSAvoidversion management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The application performs version checking and determines the appropriate resource version in advance, before the user actually requests a visualization. This preliminary determination of resource version eliminates the need for repeated checks during each visualization operation, reducing processing time and complexity while ensuring up-to-date resources are used.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application retrieves and stores local copies of application resources in different versions, allowing it to quickly determine which version to use without repeatedly checking the source system. The system maintains local copies of resource version information and can rapidly switch between versions based on the specific visualization requirements.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10817281B2Packaged application resources for mobile applications
Publication Date: 2020.10.27 SAP SE
  • US10817281B2 patent drawing
  • US10817281B2 patent drawing
  • US10817281B2 patent drawing

AI summary

Some embodiments provide a program. The program receives through an application operating on the mobile device a request for a set of visualizations of data. The program further determines a version of application resources to use for generating the set of visualizations of data. Based on the version of application resources, the program also determines whether a set of application resources having the version is included in the application. Upon determining that the set of application resources having the version is included in the application, the program further uses the set of application resources to generate the set of visualizations of data. Upon determining that the set of application resources having the version is not included in the application; the program also retrieves the set of application resources from a computing system and using the retrieved set of application resources to generate the set of visualizations of data.