Microapp Action Invocation via Contextual UI Elements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for accessing and interacting with multiple applications lack the ability to seamlessly invoke microapp actions without switching context or launching the resource access application, limiting user productivity by requiring full application launches and context changes.
Innovation Solution
A system that allows microapp actions to be invoked from user applications by tagging them to indicate additional user interface controls, enabling users to perform actions directly within the launched application, such as Salesforce, using embedded browsers or remote access engines like Citrix Workspace, without needing to switch context, by presenting special user interface elements based on tags assigned to microapp actions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If full application launches are required to access microapp actions, then application functionality is complete, but user productivity decreases due to context switching and time loss
Solution Approach 1:
The patent embeds microapp actions within the existing application interface by presenting special user interface elements (such as right-click context menus or toolbars) that allow users to invoke microapp actions without launching a separate application. This nesting approach enables actions like pushing tasks to Trello to be performed directly within Salesforce, eliminating the need for full application launches and context switching.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a resource access application or gateway that mediates between the user application and the microapp service. This intermediary presents special user interface elements that bridge the gap between the current application context and the microapp action, allowing seamless invocation without requiring the user to switch to a different application window.
2Ease of operation
If microapp actions are integrated within applications, then ease of operation improves, but device complexity increases due to additional user interface elements and integration mechanisms
Solution Approach 1:
The patent segments the user interface into standard application elements and special microapp action elements. The special user interface elements (such as context menus, toolbars, or floating panels) are presented as distinct, modular components that can be dynamically added to the application interface based on the current context, allowing easy integration without permanently complicating the base application structure.
Solution Approach 2:
Instead of fully integrating microapp actions into the application's core functionality, the patent uses partial integration by presenting special user interface elements that provide access to microapp actions on-demand. This approach provides sufficient functionality for common tasks without the complexity of full integration, allowing users to access microapp actions only when needed through contextual interfaces.
Data Source
AI summary
In one disclosed method, a first application accessed by a client device receives an indicator of an action that a second application is configured to take with respect to a third application. The client device accesses a fourth application and presents, based at least in part on the indicator received by the first application, a user interface element for the fourth application. Based at least in part on detecting selection of the user interface element, the client device presents a user interface configured to cause the second application to take the action with respect to the third application in response to a user input. The client device detects the user input to the user interface and causes, based at least in part on the user input, the second application to perform the action with respect to the third application.