Modular Native App Updates via Shell and VM

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Native mobile applications require complete reinstallation for updates, leading to increased file size, install time, and lack of modularity, while hybrid applications lack native user experience and cannot be updated efficiently.

Innovation Solution

A method for providing modular updates to natively rendered mobile applications using an application shell and virtual machine, allowing for partial code updates and in-app purchases without replacing the entire application, enabling cross-platform compatibility and native rendering.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a native application is updated, then the application receives new features and fixes, but the entire application must be downloaded and re-installed

Engineering Contradiction:

Improveapplication update capabilityVSAvoidupdate install time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The application is divided into a native application shell and separate downloadable code modules. The shell remains on the device while individual code modules can be updated independently, allowing partial updates rather than full application reinstallation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The code portion of the application is extracted from the native application shell and stored separately on a server. This allows the code to be updated and downloaded independently from the native shell, enabling incremental updates without replacing the entire application.

Inventive Principle:

Principle #2Taking out (Extraction)

2Reliability

If a native application is updated, then the application receives new features and fixes, but the entire application file size must be downloaded

Engineering Contradiction:

Improveapplication update capabilityVSAvoidupdate file size

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The application code is segmented into separate modules that can be downloaded individually. Only the specific code modules that need updating are downloaded, rather than the entire application package, significantly reducing the update file size.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The code is extracted from the native application shell and stored separately. This separation allows the system to download only the necessary code updates rather than the complete application, reducing the quantity of data transferred.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If a native application is updated, then the application receives new features and fixes, but the update process is complex and time-consuming

Engineering Contradiction:

Improveapplication update capabilityVSAvoidupdate process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The application shell automatically checks for updates, downloads new code modules, and replaces old modules without requiring user intervention or complex update management. The system self-manages the update process, reducing complexity for both developers and users.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The application shell provides universal functionality across different platforms and application types, handling update management, code execution, and native feature access in a unified manner, simplifying the overall update process.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of manufacture

If hybrid application is used, then the application can be updated easily via web server, but the user experience is not native

Engineering Contradiction:

Improveupdate simplicityVSAvoiduser experience quality

Core Design Contradiction:

Ease of manufactureVSEase of operation

Solution Approach 1:

The invention merges the advantages of hybrid applications (easy code updates via web server) with the advantages of native applications (native rendering and user experience). The native application shell provides native UX while downloading and executing code modules similarly to hybrid applications, achieving both goals simultaneously.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS10248403B2Providing updates for natively rendered mobile applications

Publication Date: 2019.04.02 KONY INC

AI summary

Systems and methods for providing an update to a natively rendered application installed on a mobile device are provided. A method includes sending a message to a server, wherein the message includes identifying information about the application. The method also includes receiving an update from the server in response to the message, wherein the update comprises a module of code that corresponds to less than the entire application. The method further includes updating the application using the received update. The method additionally includes executing the application after the updating. The method also includes, based on the executing the application, natively rendering the application using the operating system of the mobile device.