Embedded Component Mediates Cross-Platform Permission Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating independent computer applications to share features is hindered by technical compatibility issues and the computational expense of replicating functionalities, leading to a disjointed user experience and inefficient resource utilization.
Innovation Solution
A computer-implemented method that provides a unified frontend for users while maintaining separate backend systems, allowing a primary application to communicate with secondary applications and retrieve services, eliminating the need for feature replication by using an embedded component to manage interactions and permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If features from one computer application are developed into another computer application, then the features can be integrated, but it is too computationally expensive and requires many man hours while potentially not replicating the quality of the original features
Solution Approach 1:
The patent introduces an intermediary component (embedding component in the primary application that communicates with the secondary application) that acts as a mediator between two independent applications. This allows features to be integrated without direct modification of either application's codebase, avoiding the computational expense and quality loss of feature replication while maintaining functional integration.
Solution Approach 2:
The patent segments the integrated system into independent primary and secondary applications, each maintaining their own backend systems and codebases. The embedding component creates a modular interface that allows feature integration while preserving the independence and quality of each original application, avoiding the need to merge codebases which would be computationally expensive.
2Reliability
If two existing computer applications are integrated by solving technical compatibility issues, then they can function together cohesively, but the process is complex and time-consuming
Solution Approach 1:
The embedding component serves as an intermediary that handles communication and coordination between the primary and secondary applications. It manages permission checks, data exchange, and session coordination, thereby achieving cohesive functionality without requiring complex direct integration between the two applications' backend systems.
Solution Approach 2:
The embedding component provides universal functionality that works across different application types and backend systems. It implements a standardized interface for permission checking, data retrieval, and session management that can accommodate various primary and secondary application combinations, reducing integration complexity through a multi-functional approach.
3Adaptability or versatility
If features are integrated by developing them into the second application, then integration is achieved, but it may not replicate the quality of the first application's features which have been refined over time
Solution Approach 1:
The embedding component acts as a faithful intermediary that accesses and exposes the secondary application's features exactly as they exist in their original, refined state. Rather than copying or adapting features, it provides direct access to the original implementation, thereby preserving the quality and refinement that has been developed over time in the source application.
Data Source
AI summary
Systems and methods for integrating computer applications is disclosed. A method includes receiving, at a secondary product platform, a first permission check request for a user of a primary client; determining, via a second backend system, whether the user is licensed for the secondary product platform; upon determining the user is not licensed, generating and communicating a second permission check request to a first backend system of a primary product platform; receiving, from the first backend system, an indication the user is associated with a permission maintained and checked via the primary product platform; upon receiving the indication, determining whether the project of the primary product platform is linked to a corresponding space of the secondary product platform associated with a resource; granting access, via the second backend system, to the resource for a current session that will expire at the end of the current session.