Helper SDK for Hybrid App Native Device Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Native applications face challenges with full third-party SDKs due to increased size and maintenance efforts, and web application SDKs lack access to native device capabilities, limiting functionality and user experience.

Innovation Solution

A hybrid implementation using a small native Helper SDK that communicates with a web application to access native device functions, such as camera, GPS, and secure memory, while maintaining a smaller application size and reduced maintenance requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a full third-party SDK is included in a native application, then the application gains access to expanded functionality and native device capabilities, but the application size increases significantly and maintenance becomes more difficult

Engineering Contradiction:

Improveaccess to native device capabilitiesVSAvoidapplication size

Core Design Contradiction:

Adaptability or versatilityVSWeight of stationary object

Solution Approach 1:

The patent segments the SDK functionality into two parts: a minimal native Helper SDK included with the application that provides only device capability access, and a web-based SDK that provides the full functionality. This segmentation allows the application to gain access to native device capabilities through the Helper SDK while keeping the application size small, as the bulk of the SDK functionality resides in the web-based component that is loaded separately.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a web view as an intermediary component that bridges the native application and the web-based SDK. The Helper SDK in the native application communicates with the web view, which then interacts with the full web-based SDK. This intermediary approach enables the native application to access expanded functionality through the web view without directly including the full SDK, thereby maintaining a small application size while achieving versatility.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a full third-party SDK is included in a native application, then the application gains access to expanded functionality, but updates become more difficult due to multiple parties involved

Engineering Contradiction:

Improveexpanded functionalityVSAvoidmaintenance difficulty

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

By segmenting the SDK into a minimal native Helper SDK and a web-based SDK, the patent enables independent updates of each component. The web-based SDK can be updated by the third-party provider without requiring updates to the native application, as it is delivered through the web server and loaded by the web view. This segmentation simplifies maintenance by allowing separate update cycles for the native and web components.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent makes the SDK configuration dynamic by allowing the native application to load different web-based SDK versions from a web server. The Helper SDK communicates with the web view, which dynamically loads the appropriate web-based SDK functionality. This dynamic approach enables flexible updates and adaptations without requiring recompilation or redistribution of the native application, thereby improving ease of manufacture and maintenance.

Inventive Principle:

Principle #15Dynamics

3Weight of stationary object

If a web application SDK is used, then the application size remains small, but access to native device capabilities is limited due to browser function limitations

Engineering Contradiction:

Improveapplication sizeVSAvoidaccess to native device capabilities

Core Design Contradiction:

Weight of stationary objectVSAdaptability or versatility

Solution Approach 1:

The patent uses the Helper SDK as an intermediary that runs in the native application environment and has direct access to native device capabilities. The Helper SDK acts as a bridge, receiving requests from the web view and translating them into native device function calls. This intermediary approach enables the web-based SDK to access native device capabilities that would otherwise be unavailable due to browser limitations, while maintaining the benefits of a small application size.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimension to the architecture by introducing a hybrid layer that combines native and web-based components. The Helper SDK provides a native layer that supplements the web-based SDK, enabling access to native device capabilities through a different dimensional approach. This hybrid architecture allows the system to leverage both the small size advantage of web applications and the native capability access of native applications, effectively adding a new dimensional solution to the problem.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11106476B2Helper software developer kit for native device hybrid applications

Publication Date: 2021.08.31 VISA INTERNATIONAL SERVICE ASSOCIATION

AI summary

A helper SDK embedded in a native application performs local operations on behalf of a web application affiliated with the helper SDK. The helper SDK may perform security functions such as fingerprint or face biometric verifications as well as access device-specific hardware such as a camera or secure memory. The web application may use an 0Auth technique for access and refresh tokens. In a transaction system, when a user is confirmed via the security function, order details are passed to the web application with a refresh token and ciphertext confirmation data is returned to the native application for completion of the transaction.