Super App Integration Using Shared Data and Background API Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current methods for building super applications are cumbersome, requiring independent module creation and integration, and face issues with third-party service reliability and security, especially when integrating multiple applications.

Innovation Solution

A computer-implemented method using an APP development tool to create a super application by selecting a main application, establishing data transfer paths and API associations between multiple applications, ensuring interoperability and flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing APPs are integrated into a super APP by independent module creation, then multiple services can be provided in one application, but the development process becomes cumbersome and complex

Engineering Contradiction:

Improvemultiple services in one applicationVSAvoiddevelopment process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the super APP into independent modular components (main APP and slave APPs) that can be separately developed and then integrated. Each slave APP is packaged as an independent module with its own API interface, allowing the complex super APP to be built by assembling simpler, pre-defined modules rather than creating everything from scratch.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an information transfer manager as an intermediary component that handles communication between the main APP and slave APPs. This mediator simplifies the integration process by providing standardized data transfer mechanisms, eliminating the need for developers to manually configure complex communication protocols between modules.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If third-party services are integrated into the application, then additional functionality is achieved, but reliability and security issues arise

Engineering Contradiction:

Improvethird-party service integrationVSAvoidservice reliability and security

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent uses an information transfer manager as an intermediary layer between the application and third-party services. This mediator handles all external communications through standardized APIs, providing a secure and reliable interface that isolates the core application from potential security vulnerabilities in third-party services.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent requires that slave APPs pre-define their API interfaces and data transfer protocols before integration. This preliminary specification of interaction protocols ensures that reliability and security requirements can be established and enforced before the actual integration occurs, allowing for proactive rather than reactive security management.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If multiple applications are integrated into a super APP, then a one-stop solution is achieved, but the integration process is difficult

Engineering Contradiction:

Improveone-stop solution capabilityVSAvoidintegration ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the integration process into clear, manageable steps: selecting the main APP, adding slave APPs as independent modules, and automatically establishing communication paths through the information transfer manager. This segmentation transforms the complex integration task into a series of simple, standardized operations.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal integration framework where the same information transfer manager and API execution mechanisms work for all slave APPs regardless of their specific functionality. This universal approach simplifies integration by eliminating the need for custom integration logic for each service, allowing developers to easily add new functionalities using the same standardized process.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP4647897A1Computer-implemented method for building super application, computer program and computer-readable data carrier

Publication Date: 2025.11.12 TATUNG UNIVERSITY

Figure 1~2
Figure 3
Figure 4

AI summary

Disclosed is a method for building a super application (20, 600). An application (APP) development tool (700) is used for selecting a main APP (200, 601) and one or more slave APPs (100, 100-1, 100-2, 100-3, 602, 610, 620), and the main APP (200, 601) creates the information transfer manager (240) and the background application programming interface (API) executor (250). The information transfer manager (240) is responsible for storing the data content passed by each APP in the super APP (20, 600), and allows each APP to read the data content through the information transfer manager (240). Moreover, the background API executor (250) calls the content of a background API executable master file (120, 120-1, 120-2, 120-3, 220, 610-2, 620-2) of other APPs to execute the content in the main APP (200, 601). Accordingly, multiple APPs may be combined into one super APP (20, 600).