Dynamic Mobile App Generation via Server Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile applications require extensive development time and increased costs for updates due to static user interfaces, and the need for separate code development for various operating systems, leading to delayed updates and increased product costs.

Innovation Solution

A dynamic generation method for mobile applications using a lightweight container application that synthesizes browser and native operating system functionalities, allowing for a customizable user interface generated on the fly based on context data, with a configuration file created by a server and displayed as native to the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional mobile applications are updated with new features or interface changes, then the application functionality is improved, but extensive development time and repackaging are required

Engineering Contradiction:
Improveapplication update capabilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The application is segmented into a static native container component and a dynamic web-based interface component. The container provides stable native functionality while the web interface can be independently updated without repackaging the entire application.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A web browser component acts as an intermediary between the native operating system and the application logic. This allows web-based interfaces to be updated and deployed independently from the native container, enabling rapid updates without full repackaging.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate application code is developed for each operating system, then native functionality and performance are optimized, but development effort and costs increase

Engineering Contradiction:
Improvenative functionalityVSAvoiddevelopment effort
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A single universal container application is developed that can run on multiple operating systems. The container provides cross-platform compatibility while maintaining access to native functionalities through the web browser interface, eliminating the need for separate native code development for each platform.

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

Solution Approach 2:

The traditional mechanical approach of writing separate native code for each platform is replaced with a web-based approach. HTML, CSS, and JavaScript serve as universal languages that can be executed within native containers across different operating systems, reducing development complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Device complexity

If a static user interface is used in mobile applications, then the application structure is simple, but updates require complete repackaging and redistribution

Engineering Contradiction:
Improveapplication structureVSAvoidupdate deployment
Core Design Contradiction:
Device complexityVSEase of manufacture

Solution Approach 1:

The user interface transitions from a static native structure to a dynamic web-based structure. The web interface can be updated, modified, and deployed independently without requiring complete repackaging of the native container, enabling agile updates while maintaining simple container structure.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS8918712B2Dynamically generating a mobile application
Publication Date: 2014.12.23 FMR CORP
  • US8918712B2 patent drawing
  • US8918712B2 patent drawing
  • US8918712B2 patent drawing

AI summary

Methods and apparatuses, including computer program products, are described for dynamically generating a mobile application. A server receives a request from a mobile device to launch an application on the mobile device. The server generates a configuration file based on the launched application. The server transmits the configuration file to the mobile device for generation of a user interface of the launched application using the configuration file. The user interface includes a first display area using browser functionality of the mobile device to display one or more web page elements formatted by the server to appear as native to the mobile device. The user interface further includes a second display area having one or more interface elements that are native to an operating system of the mobile device.