Automated Mobile App Fusion Platform for Codeless Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current methods for integrating mobile applications across multiple platforms and enterprise systems are resource-intensive, time-consuming, and often require significant development effort, with existing solutions like SDKs and app wrappers being vendor-specific, platform-specific, and lacking universality, leading to functionality limitations and compatibility issues.

Innovation Solution

An automated mobile app fusion platform (AFP) that allows for rapid integration of third-party functions into mobile apps without requiring source code access, enabling seamless integration of various services and security capabilities across multiple platforms through a cloud-based, codeless workflow.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If SDKs are used for mobile app integration, then integration capability is provided, but development effort and complexity increase significantly

Engineering Contradiction:

Improveintegration capabilityVSAvoiddevelopment effort

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary integration layer that sits between the mobile app and enterprise services, automatically handling integration logic. This mediator component provides the needed integration capability without requiring developers to directly implement complex SDK integrations, thus reducing development effort while maintaining adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal integration platform that can work with multiple different enterprise services and mobile platforms through a single interface. This multi-functional system eliminates the need for separate SDK integrations for each service, reducing overall development complexity while providing broad integration capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If multiple quality assurance and release cycles are implemented for integration, then integration quality improves, but deployment time increases significantly

Engineering Contradiction:

Improveintegration qualityVSAvoiddeployment time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary integration testing and validation within the integration platform itself before deployment. By performing quality assurance checks in advance during the integration process rather than through multiple post-deployment release cycles, the system ensures integration quality while significantly reducing the time lost to repeated testing and re-release cycles.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If vendor-specific SDKs are used for each service, then service-specific functionality is achieved, but overall integration effort across multiple projects remains heavy

Engineering Contradiction:

Improveservice-specific functionalityVSAvoidintegration efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Productivity

If app wrappers are used for faster integration, then integration speed improves, but functionality limitations and unpredictable behavior occur

Engineering Contradiction:

Improveintegration speedVSAvoidapp behavior consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11294663B2Automated mobile application integration

Publication Date: 2022.04.05 APPDOME LTD

AI summary

Systems, methods, devices and non-transitory, computer-readable storage mediums are disclosed for automated mobile app integration. In an embodiment, a method comprises: receiving, by a server computer from a development system, a first application binary executable for an application; receiving, by the server computer, a dataset specifying mobile services to be added to the application, the dataset selected by a user of the development system; dynamically and automatically generating a software adapter for adapting one or more plugin software components to the first app binary executable according to the dataset; generating, by the server computer and without access to source code for the first application binary executable, a second application binary executable for the application, the generating including merging the first application binary executable with binary code for the adaptor and the plugin software components; and transmitting, by the server computer to the development system, the second application binary executable.