Enterprise App View Mobilization via Dynamic Interface Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for mobilizing enterprise applications for mobile devices are costly, time-consuming, and often result in reduced functionality compared to their PC counterparts, with limited scalability and high overheads due to the need for re-development or third-party solutions.

Innovation Solution

A system and method for automatically converting non-mobile computer platform application views to mobile application views by transforming them based on differences in display capability, peripheral devices, bandwidth, and software libraries, utilizing a cloud-based backend for dynamic interface transformation and intelligent traffic suppression, enabling rapid and scalable mobilization without re-development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing techniques are used to mobilize enterprise applications for smartphones, then application functionality can be accessed on mobile devices, but the process becomes prohibitively expensive and time consuming

Engineering Contradiction:
Improvemobile accessibilityVSAvoidmobilization time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-processing and analyzing the desktop application structure, interface elements, and data flow before actual mobilization begins. This includes generating a mobile-compatible representation model in advance, which significantly reduces the time required for the actual conversion process when deployment is needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention creates a simplified copy or representation of the desktop application specifically tailored for mobile devices. Instead of fully redeveloping the application, the system generates a mobile view that copies essential functionality and interface elements from the desktop version, adapting them to mobile constraints while maintaining core application behavior.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If existing techniques are used to mobilize enterprise applications for smartphones, then application functionality can be accessed on mobile devices, but the process becomes prohibitively expensive

Engineering Contradiction:
Improvemobile accessibilityVSAvoidmobilization cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system implements a universal mobilization framework that can handle multiple types of enterprise applications through a single automated process. The platform-independent approach allows the same toolset to convert applications from different desktop environments to mobile formats, eliminating the need for separate development teams for each application type and significantly reducing overall costs.

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

Solution Approach 2:

The mobilization process is designed to be self-service oriented, where the system automatically analyzes, converts, and deploys mobile applications without requiring extensive manual intervention from developers. The automated generation of mobile views and handling of platform-specific adaptations reduces labor costs and enables organizations to mobilize applications independently.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If existing techniques are used to mobilize enterprise applications, then applications can run on mobile devices, but functionality is reduced compared to PC counterparts

Engineering Contradiction:
Improvemobile operationVSAvoidapplication functionality
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system applies local quality by selectively adapting specific portions of the application interface and functionality based on mobile device characteristics. Critical functions are preserved and optimized for mobile interaction, while non-essential features are simplified or removed. The interface layout, input methods, and data presentation are locally optimized for mobile screens and touch interaction.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The mobile application view is designed to be dynamic, automatically adjusting its functionality and interface based on the mobile device's capabilities, screen size, and available resources. The system dynamically loads only the necessary application components and data for the current mobile context, ensuring optimal performance while maintaining access to full application functionality when needed.

Inventive Principle:
Principle #15Dynamics

4Productivity

If traditional mobilization approaches are used, then applications can be accessed on mobile devices, but scalability is limited and overheads are high

Engineering Contradiction:
Improvemobilization efficiencyVSAvoidsystem overhead
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer or abstraction model that sits between the desktop application and the mobile device. This intermediate representation model handles the complexity of platform-specific adaptations, allowing the core application logic to remain unchanged while enabling scalable deployment across multiple mobile devices and platforms without increasing overall system overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9880796B2Rapid view mobilization for enterprise applications
Publication Date: 2018.01.30 GEORGIA TECH RES CORP
  • US9880796B2 patent drawing
  • US9880796B2 patent drawing
  • US9880796B2 patent drawing

AI summary

Certain embodiments of the invention may include systems, methods, and computer readable media for automatically converting a non-mobile computer platform application view to a mobile application view for use on a mobile device. The method can include transforming the non-mobile computer platform application view to the mobile application view based at least in part on differences between the-non mobile computer platform and the mobile device, wherein the differences comprise one or more of display capability, associated peripheral devices, bandwidth, or software libraries. The method can also include sending information associated with the transformed application view to the mobile device.