Version Control Module for Web-Native App Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile app development platforms, such as React Native, do not allow seamless integration of JavaScript-based web components with native code, requiring developers to rewrite native applications for compatibility, resulting in significant resource and time costs.

Innovation Solution

A mobile app development platform that integrates web-based components or mini apps written in JavaScript with native code using a cross-platform information exchange mechanism and automatic API generation, allowing bi-directional communication and version control, thus enabling the reuse of existing code and resources without requiring developers to understand or rewrite source code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If web-based components are integrated with native code using a cross-platform information exchange mechanism, then code reuse and development efficiency are improved, but system complexity and version control challenges increase

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system is divided into distinct components: a version control module that manages web-based components separately from the native application code. This segmentation allows independent version control of web components without affecting the native codebase, thereby improving development efficiency while managing system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A cross-platform information exchange mechanism acts as an intermediary layer between web-based components and native code. This mediator handles communication and data exchange, enabling code reuse across platforms while abstracting the complexity of integration details from developers.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of repair

If real-time updates of web-based components are enabled, then software maintenance and updates are improved, but version compatibility and integration stability may deteriorate

Engineering Contradiction:
Improvesoftware maintenanceVSAvoidintegration stability
Core Design Contradiction:
Ease of repairVSReliability

Solution Approach 1:

The version control module performs preliminary version checking and compatibility validation before allowing updates to web-based components. This preliminary action ensures that updated components are compatible with the native application version, maintaining integration stability while enabling easy software maintenance and updates.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If automatic API generation is implemented for bi-directional communication, then integration capability is improved, but system complexity and development overhead increase

Engineering Contradiction:
Improveintegration capabilityVSAvoiddevelopment overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements automatic API generation that creates bi-directional communication interfaces between web-based components and native code without requiring manual intervention. This self-service mechanism enhances integration capability by automatically adapting to different component types while reducing the visible development overhead for developers.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10379846B1Systems and methods for real time version control for integrating updated web-based components with a native application
Publication Date: 2019.08.13 WALMART APOLLO LLC
  • US10379846B1 patent drawing
  • US10379846B1 patent drawing
  • US10379846B1 patent drawing

AI summary

An approach is proposed to support version control for integrating updated web-based components with a native application of a mobile device. A new version of a mini app is received at an application version control module configured to control versioning of the mini app and the native application, wherein the mini app includes one or more web-based features in JavaScript to be integrated with the native application. Version compatibility checks are performed to confirm that the new version of the mini app only contains native dependencies that match with a version of the native application the version of the mini app depends on. The new version of the mini app is integrated with the native application into the target mobile application if the version compatibility checks pass. Finally, the target mobile application is uploaded to an app store to make the target mobile application available to an end user.