Façade Framework Unified Codebase Web Hybrid Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional web applications cannot access local resources, requiring separate development and maintenance of codebases for hybrid and web versions, leading to increased development time and resource inefficiency.

Innovation Solution

A façade framework that provides a unified interface for web and hybrid applications, using a web library and hybrid library with shared APIs, enabling a single codebase to serve both web and hybrid versions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate codebases are maintained for web and hybrid applications, then each version can be optimized for its specific platform, but development time increases and resource efficiency decreases

Engineering Contradiction:
Improveplatform optimizationVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent merges web and hybrid application codebases into a unified codebase that can be compiled and deployed to both platforms. The build system combines source files, web assets, and configuration files into a single deployment package that serves both web and hybrid applications, eliminating the need to maintain separate codebases while preserving platform-specific optimizations through conditional compilation and platform-aware asset selection.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal build system and unified codebase structure that serves multiple purposes: it can generate both web and hybrid applications from the same source code. The system provides universal asset management, configuration handling, and compilation processes that adapt to different target platforms, allowing a single codebase to fulfill multiple deployment requirements simultaneously.

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

2Adaptability or versatility

If separate codebases are maintained for web and hybrid applications, then platform-specific requirements can be met, but resource efficiency decreases due to duplicate maintenance

Engineering Contradiction:
Improveplatform compatibilityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges web and hybrid application codebases into a unified codebase that can be compiled and deployed to both platforms. The build system combines source files, web assets, and configuration files into a single deployment package that serves both web and hybrid applications, eliminating the need to maintain separate codebases while preserving platform-specific optimizations through conditional compilation and platform-aware asset selection.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the unified codebase into distinct components: shared source files, platform-specific assets, and configuration files. This segmentation allows the build system to selectively include or exclude components based on the target platform, maintaining platform compatibility while avoiding duplication of maintenance efforts across separate codebases.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If web applications use conventional web APIs, then cross-platform compatibility is supported, but access to local resources and native APIs is prevented

Engineering Contradiction:
Improvecross-platform compatibilityVSAvoidresource access limitation
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The patent introduces an intermediary build system and unified codebase structure that mediates between web application requirements and native resource access. The system translates web-based asset references into platform-specific paths and configurations during the build process, enabling web applications to access local resources and native APIs through the hybrid application deployment while maintaining cross-platform compatibility through the unified codebase approach.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9471303B2Façade framework for IDE
Publication Date: 2016.10.18 SAP SE
  • US9471303B2 patent drawing
  • US9471303B2 patent drawing
  • US9471303B2 patent drawing

AI summary

A framework for developing web and hybrid applications (Apps) of a project is described herein. In accordance with one aspect, a façade framework is provided. The façade framework includes a web library having a set of application program interfaces (APIs) of hybrid features of a mobile device, a hybrid library having a set of APIs of hybrid features of a mobile device, and a unified interface for interfacing with the web and hybrid libraries. Base code of a base project may be provided using an application development system. The base code may include common code to web assets common to the web and hybrid Apps of the project. The base code may be extended using the application development system to produce an extended code of the project, where the extended code includes hybrid features used by the project. The unified interface provides APIs from the web and hybrid libraries used by the project. The façade framework enables the extended code to serve as a unified code solution to both web and hybrid App of the project.