Container App Integrating Microapps via APIs for Financial Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face difficulties with managing multiple distinct applications for financial transactions on mobile devices, including remembering credentials, creating accounts, and security risks associated with sharing financial information across various apps.
Innovation Solution
A computing system and method that integrates microapps into a container application, using APIs to manage and secure transactions, store user information, and control user experience, providing a centralized platform for accessing multiple microapps while maintaining security and ease of use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users install and use multiple distinct applications for financial transactions, then they can access diverse financial services, but they face difficulties in remembering credentials and managing accounts
Solution Approach 1:
The container application serves as a universal platform that hosts multiple microapps for different financial services. Users access diverse financial services through a single container app, eliminating the need to manage separate credentials for each application while maintaining access to diverse functionalities.
Solution Approach 2:
Microapps are nested within the container application, with each microapp representing a specific financial service. This nested structure allows users to access multiple services through a single entry point, simplifying credential management while preserving service diversity.
2Adaptability or versatility
If users create accounts with each distinct application, then they can access application-specific features, but the process becomes cumbersome
Solution Approach 1:
The container application implements a universal authentication system that provides access to all nested microapps through a single account. Users create one account in the container app and gain access to multiple financial services, eliminating repeated account creation while maintaining service-specific features.
Solution Approach 2:
The container application performs preliminary authentication setup that applies to all nested microapps. By establishing credentials at the container level before users access individual microapps, the system eliminates the need for repeated account creation across multiple services.
3Ease of operation
If users share financial information across multiple distinct applications, then they can use convenient services, but security risks increase
Solution Approach 1:
Microapps are nested within the container application with controlled access to financial information. The container app acts as a security layer that manages data sharing, allowing convenient service access while reducing security risks through centralized information protection.
Solution Approach 2:
The container application serves as an intermediary between users and microapps, managing financial information securely. It mediates data access by providing necessary information to microapps without exposing raw financial data, thus maintaining service convenience while enhancing security.
Data Source
AI summary
A computing system (100) that includes at least one microapp (202) and a container application (204) configured to receive an application output from the microapp(s) (202,602) via an application programming interface. The computing system (100) can include at least one processor (112,132) and at least one tangible, non-transitory computer-readable medium that stores instructions that, when executed by the at least one processor (112,132), cause the at least one processor (112,132) to perform operations. The operations can include providing, for display within a first panel (304) in a user interface (306), a navigation bar (302) based on data received from the container application (204); receiving, at the container application (204), the application output from the at least one microapp (202) via the application programming interface; and providing, for display within a second panel in the user interface (306), data describing the application output.