Hybrid Mobile App Generation via Browser-Based Dependency Analysis

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In the iterative development process of enterprise mobile applications, identifying and managing dynamic dependencies within a browser-based development environment is challenging due to the complexity and variability of application components.

Innovation Solution

A system comprising a web Integrated Development Environment (IDE) with a dependency analysis engine, component retrieval engine, component build engine, and packaging engine that analyzes configuration files, retrieves and builds dependent components, and packages them into an application asset package, enabling hybrid mobile application development and deployment across various platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If developers use browser-based development tools for iterative development of enterprise mobile applications, then development flexibility and accessibility are improved, but identifying and managing dynamic dependencies becomes more challenging

Engineering Contradiction:

Improvedevelopment accessibilityVSAvoiddependency identification

Core Design Contradiction:

Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements automated feedback mechanisms by continuously analyzing application code and configuration files to identify dependencies. The dependency analysis engine provides real-time feedback to developers about identified dependencies, their relationships, and impact analysis, enabling informed decision-making during iterative development without leaving the browser-based environment.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary dependency analysis engine that acts as a mediator between the development environment and the application code. This engine automatically analyzes code, retrieves configuration files, and generates dependency information, bridging the gap between simple browser-based development and complex dependency management requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the development environment supports dynamic changes to applications, then adaptability is improved, but dynamically identifying dependencies in iterative development becomes more challenging

Engineering Contradiction:

Improveapplication adaptabilityVSAvoiddependency management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system embraces dynamics by implementing a dependency analysis engine that continuously adapts to changing application code and configuration files. The engine performs incremental analysis rather than static analysis, automatically detecting new dependencies as code changes occur during iterative development, thus managing complexity dynamically rather than statically.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent applies preliminary action by proactively analyzing code and retrieving configuration files before dependency issues manifest. The system pre-identifies potential dependencies and their relationships, preparing dependency information in advance to guide development decisions and prevent complexity accumulation during iterative changes.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If developers manually track dependencies in iterative development, then control over dependencies is improved, but development time and productivity are reduced

Engineering Contradiction:

Improvedependency controlVSAvoiddevelopment speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system implements self-service by enabling the dependency analysis engine to automatically analyze code, retrieve configuration files, and generate dependency information without requiring manual developer intervention. This automated self-service approach maintains reliable dependency tracking while freeing developers to focus on productive development activities, thereby resolving the contradiction between control and productivity.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of tracking dependencies with an automated computational system. The dependency analysis engine uses programmatic analysis of code and configuration files to identify and manage dependencies, substituting manual mechanical tracking with automated information processing, thus improving both reliability and productivity simultaneously.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9952835B2Generation of hybrid enterprise mobile applications in cloud environment

Publication Date: 2018.04.24 SAP SE

AI summary

Generate hybrid enterprise mobile applications in cloud environment, according to one embodiment. A web application is selected in a web integrated development environment (IDE) executing in a browser. The web application may depend on various components and the dependent build components may reside on different repositories. Dependency analysis engine determines the dependent build components corresponding to the web application. The component retrieval engine retrieves the dependent build components from corresponding repositories to memory or cache of the browser where the web IDE is executing. Component build engine builds the dependent build components to a build result. Packaging engine packages the build result to a single package as an application asset package. The application asset package is received in a platform dependent build service. The application asset package is built as a hybrid mobile application in the platform dependent build service. The hybrid mobile application is published in an application store.