Local SDK Platform Inter-Application Communication via Deep Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software development kits (SDKs) lack efficient mechanisms for inter-application communication and data sharing, making it difficult for applications to seamlessly interact and provide targeted actions across different applications on a computing system.
Innovation Solution
A local SDK platform with an application discovery module and inter-application communication module enables applications to share data and communicate, generating deep links to trigger actions in other applications based on data collected, facilitating communication between applications and backend services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional SDKs are used without inter-application communication mechanisms, then application development is simpler, but applications cannot efficiently share data and communicate with each other
Solution Approach 1:
The patent introduces an inter-application communication module as an intermediary component within the SDK platform. This module enables applications to communicate and share data through standardized interfaces without requiring direct integration between each application pair, thus achieving versatile inter-application communication while managing complexity through centralization.
Solution Approach 2:
The SDK platform is designed with universal communication mechanisms that can serve multiple applications and multiple types of interactions simultaneously. The inter-application communication module provides a unified framework that handles various communication scenarios (data sharing, triggering actions, deep linking) through a single versatile system rather than separate mechanisms for each case.
2Ease of operation
If deep linking mechanisms are implemented across applications, then user experience is enhanced through seamless navigation, but the system complexity increases due to additional modules required
Solution Approach 1:
The SDK platform pre-establishes deep linking mechanisms and communication protocols during the development phase. Applications are configured with deep link structures and communication capabilities beforehand, allowing seamless user navigation to occur automatically when needed, rather than implementing complex runtime decision-making logic.
Solution Approach 2:
The inter-application communication module and deep linking system are designed to operate autonomously once configured. The system automatically handles link generation, routing, and application launching without requiring manual intervention or complex control logic, thus improving ease of operation while keeping the platform structure manageable.
3Adaptability or versatility
If data collection and deep link generation are performed by non-core SDK modules, then targeted actions and advertisements can be delivered, but the loss of information increases due to data handling requirements
Solution Approach 1:
The patent extracts data collection and processing functions into separate non-core SDK modules that operate independently from the core platform. These modules collect, process, and generate deep links based on collected data, then pass only the necessary information (deep links and action triggers) back to the core system, minimizing data handling overhead in the core platform while enabling targeted actions.
Data Source
AI summary
A computing system including a first and a second application. The first application includes a first local software development kit (SDK) platform instance, and the first local SDK platform instance includes a first non-core SDK module instance, an application discovery module, and an inter-application communication module. The second application includes a second local SDK platform instance. The first non-core SDK module instance is configured to is a request to the application discovery module. Upon receipt of the request, the discovery module is configured to determine that the second local SDK platform instance includes a second non-core SDK module instance that is configured to service the request. The first local SDK platform instance, based on the determination, is configured to generate a deep link associated with the second application based on data collected by the first local SDK platform instance and provide the deep link to the first non-core SDK module.