Cross-platform Module Loading via Web Browser

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods require developers to create multiple versions of applications and modules for different device types, leading to increased development time and resource requirements, as modules are not easily compatible across various platforms without modification.

Innovation Solution

A system and method for loading a module across multiple device types by initializing a web-based application, checking dependencies, and loading the module on a web browser, allowing it to be recognized and integrated without platform-specific modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If developers create multiple versions of applications for different device types, then compatibility across platforms is improved, but development time and resource requirements increase

Engineering Contradiction:

Improveplatform compatibilityVSAvoiddevelopment time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies universality by creating a single module format that can be loaded and executed across multiple device types including smartphones, tablets, and desktops. The module is designed with a universal structure containing identification information and functional code that can be recognized and executed by different device platforms without requiring separate versions for each device type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent utilizes parameter changes by modifying the module's identification information to indicate compatibility with specific device types. The system changes the interpretation of module parameters based on the target device, allowing the same module to be adapted to different platforms through parameter interpretation rather than creating separate module versions.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If developers create multiple versions of applications for different device types, then platform compatibility is improved, but resource requirements increase

Engineering Contradiction:

Improveplatform compatibilityVSAvoiddevelopment resources

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges the functionality that was previously distributed across multiple device-specific versions into a single unified module. By combining platform-specific adaptation logic within the module's identification information and execution environment, the system eliminates the need for separate module versions for different platforms.

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If modules are modified to conform to device platforms, then platform compatibility is improved, but module complexity increases

Engineering Contradiction:

Improveplatform compatibilityVSAvoidmodule complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts platform-specific adaptation requirements from the module's functional code and places them in the module's identification information. This separation allows the core functional code to remain simple and universal, while platform-specific details are handled through the identification information that the execution environment processes.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary execution environment that mediates between the universal module format and device-specific platforms. The execution environment interprets the module's identification information and adapts the module for execution on the target platform, eliminating the need for developers to directly modify modules for each platform.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If application emulators are used to run applications on different devices, then platform compatibility is improved, but external support requirements increase

Engineering Contradiction:

Improveplatform compatibilityVSAvoidexternal support requirements

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables modules to be self-adaptive to different platforms through embedded identification information. The module automatically indicates its compatibility requirements and the execution environment automatically adapts it for the target platform, eliminating the need for external emulator support.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS12010165B2Cross-platform module for loading across a plurality of device types

Publication Date: 2024.06.11 HYLAND SWITZERLAND SARL

AI summary

Methods for loading a module on a plurality of device types without modification includes initializing an application native to the client device, the application including a web browser; determining a module to be loaded on the application, the module written in a web-based format and having a set of dependencies indicated within a code thereof; and loading the determined module on the web browser for recognition by the application native to the client device. The loading the determined module on the web browser includes loading the set of dependencies of the module.