Cross-App User Data Management via SDK Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face frustration and increased effort when replicating data from one app to another, especially when using multiple apps that share data, as they must manually re-enter information across different applications.

Innovation Solution

A system and method where the software development kit (SDK) of a new app identifies logged-in apps on a user device and uses Application Programming Interfaces (APIs) to obtain and share user data, such as payment methods and frequent locations, to streamline account registration and configuration across multiple apps.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a user manually replicates data from one app to another, then data accuracy is maintained, but user time and effort increase significantly

Engineering Contradiction:
Improvedata accuracyVSAvoiduser time and effort
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system creates a digital copy of user data from one application and transfers it to another application through automated interfaces. Instead of manual replication, the SDK copies relevant user information (such as payment methods, profile data, or preferences) from the source application to the target application, maintaining data accuracy while eliminating manual effort.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary layer (the SDK and API system) that mediates between different applications. This intermediary automatically manages data transfer between apps, serving as a bridge that eliminates the need for direct manual user intervention while ensuring accurate data replication across application boundaries.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If an SDK automatically shares user data across multiple apps, then user effort is reduced, but data security and privacy concerns increase

Engineering Contradiction:
Improveuser effortVSAvoiddata security and privacy risks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by obtaining user consent and authorization before automatically sharing data across applications. The SDK checks whether the user has logged in and granted permission for data sharing prior to initiating automated data transfer, thereby reducing user effort during the actual data sharing process while maintaining security through pre-authorized operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors and verifies user authentication status and data sharing permissions. The SDK checks whether users remain logged in and authorized before proceeding with data sharing, providing ongoing feedback to ensure security requirements are met while maintaining automated ease of operation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10656976B2User data management across multiple apps on a user device
Publication Date: 2020.05.19 PAYPAL INC
  • US10656976B2 patent drawing
  • US10656976B2 patent drawing
  • US10656976B2 patent drawing

AI summary

Systems and methods for managing user data across multiple apps are disclosed. An example method includes, determining that an installation of a first app on a user device is completed; identifying a second app in which a user has been authenticated and has been installed on the user device; obtaining a second set of user information associated with the user from the second app; and configuring a user account of the user in the first app using the second set of user information. In some implementations, identifying the second app is executed in response to determining that the installation of the first app on the user device is completed. In some other implementations, identifying the second app is executed in response to a user selection of the first app after the installation.