Mobile RPA Workflow Design Using a Model GUI
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Automating repetitive tasks on mobile computing platforms, such as smartphones and tablets, is challenging due to their hardware and software heterogeneity and unique user interaction methods, which differ from desktop computers, requiring substantial technical knowledge and specialized tools.
Innovation Solution
A method and system for robotic process automation (RPA) that employs a model graphical user interface (GUI) to mimic a mobile device, allowing users to input gestures and select target elements, generating a computer-readable specification for an RPA robot to replicate these interactions on actual mobile devices, thus simplifying the programming and deployment of RPA on mobile platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional RPA tools designed for desktop computers are used, then automation of desktop tasks is achieved, but automation of mobile devices cannot be performed due to hardware and software heterogeneity
Solution Approach 1:
The RPA design application provides a unified graphical interface that works across multiple device types (desktop and mobile). The system abstracts device-specific complexities behind a common interface, allowing the same RPA tool to automate tasks on different platforms without requiring separate specialized tools for each device type.
Solution Approach 2:
The patent introduces an intermediary layer (the RPA design application with model GUI) that mediates between the user and the heterogeneous mobile device interfaces. This intermediary handles the complexity of different operating systems and hardware configurations, translating user actions into device-specific commands without exposing this complexity to the end user.
2Ease of operation
If specialized programming knowledge is required to automate mobile devices, then precise control over device interactions is achieved, but accessibility to non-technical users is reduced
Solution Approach 1:
The system provides self-service capabilities through automated gesture recognition and model GUI generation. When users interact with the model GUI, the system automatically captures these interactions, identifies the corresponding gestures, and generates the appropriate automation workflows without requiring users to manually program or configure complex parameters.
Solution Approach 2:
The patent replaces manual programming mechanics with automated gesture capture mechanics. Instead of requiring users to write code or configure complex settings, the system substitutes this with a simpler interaction model where users simply perform gestures on the model GUI, and the system automatically translates these into executable automation routines.
3Adaptability or versatility
If a model GUI is implemented to mimic mobile device displays, then user-friendly automation design is achieved, but system complexity increases due to rendering and interaction simulation
Solution Approach 1:
The system creates simplified copies (model GUIs) of actual mobile device interfaces. These model GUIs replicate the essential visual and interactive elements of target devices without requiring full-fidelity rendering engines. The copies are sufficient for automation design purposes while being computationally efficient to generate and manipulate.
Solution Approach 2:
The patent segments the complex task of supporting multiple device interfaces into manageable components. Rather than attempting to render and simulate all possible device interfaces simultaneously, the system divides this into separate model GUIs for different device types, each handling its specific interface characteristics independently.
Data Source
AI summary
In some embodiments, a robotic process automation (RPA) design application provides a user-friendly graphical user interface that unifies the design of automation activities performed on desktop computers with the design of automation activities performed on mobile computing devices such as smartphones and wearable computers. Some embodiments connect to a model device acting as a substitute for an actual automation target device (e.g. smartphone of specific make and model) and display a model GUI mirroring the output of the respective model device. Some embodiments further enable the user to design an automation workflow by directly interacting with the model GUI.