Software Development Pipeline for Device-Specific GUI Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software development approaches often lack comprehensive planning for optimizing user interactivity and device functionality, leading to inefficiencies and errors when extending software applications to different devices with varying operating systems and hardware.

Innovation Solution

A pipeline system for software application development that receives a software application model, determines core operations, generates functionality criteria, and creates device-specific graphical user interfaces (GUIs) to build a software application that is extendable and optimized for multiple devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a software developer uses the exact same web portal content on desktop computer as on tablet device, then development simplicity is improved, but user interactivity optimization deteriorates

Engineering Contradiction:
Improvedevelopment simplicityVSAvoiduser interactivity optimization
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the software application into device-specific versions (e.g., web portal version for desktop computers, mobile application version for tablet devices) while maintaining a unified core functionality. This allows each version to be optimized for its specific platform's user interaction patterns while avoiding the complexity of complete redesigns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal software application framework that can function across multiple device types (desktop computers, tablet devices, smartphones) while adapting its interface and functionality to each platform. The core business logic remains unified while the user interface adapts to device-specific requirements.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Loss of time

If a software developer prepares a software application for one device without consideration for other devices, then development time is reduced, but extendability to different devices deteriorates

Engineering Contradiction:
Improvedevelopment timeVSAvoidextendability to different devices
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The patent performs preliminary action by defining device-specific functionality criteria and generating device-specific graphical user interfaces during the initial planning phase. This preliminary structuring enables the software application to be efficiently extended to multiple devices without requiring extensive redesign later in the development process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent utilizes parameter changes by adjusting interface parameters, layout configurations, and interaction modes based on device characteristics. The core application logic remains unchanged while parameters such as screen layout, navigation methods, and interaction patterns are optimized for each specific device type.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If computational and functional errors occur when extending functionality to devices with different operating systems, then development simplicity is maintained, but system reliability deteriorates

Engineering Contradiction:
Improvedevelopment simplicityVSAvoidsystem reliability
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces device-specific graphical user interfaces as intermediaries between the unified core functionality and the diverse device platforms. These intermediate layers adapt the standardized functionality to platform-specific requirements, preventing direct conflicts between core logic and platform-specific behaviors that would cause computational and functional errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies local quality by tailoring specific interface components and interaction methods to match the requirements of different operating systems and device types. Each device-specific GUI is optimized for its target platform's user interaction patterns and system capabilities, ensuring reliable functionality while maintaining overall development simplicity through standardized core logic.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10996932B1Pipeline for software application development
Publication Date: 2021.05.04 INVESTCLOUD INC
  • US10996932B1 patent drawing
  • US10996932B1 patent drawing
  • US10996932B1 patent drawing

AI summary

A process receives, via a processor, a software application model. Further, the process determines, with the processor, one or more core operations to be performed by a software application to be built. The one or more core operations are based on the software application model. Additionally, the process generates, with the processor, one or more functionality criteria based on the one or more core operations. Moreover, the process generates, with the processor, one or more device-specific graphical user interfaces corresponding to each of a plurality of devices that implement the software application to be built according to the one or more functionality criteria. Finally, the process generates, with the processor, the software application based on the one or more core operations, the one or more functionality criteria, and the one or more device-specific graphical user interfaces.