Hybrid Web Application Interface Layer for Cross-Platform Hardware Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile application development methods face challenges due to platform dependency, with native applications offering high performance but limited flexibility and web applications lacking direct terminal control and performance variability.

Innovation Solution

A hybrid web application architecture that combines native and web application advantages, utilizing a system API call and web standard languages like JavaScript, HTML, and CSS, with a layered structure including a web user interface, hybrid web application interface, and cross-platform system service interface to enable platform-independent execution and hardware control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a native application development method is used, then terminal resource accessibility and performance are improved, but platform dependency increases

Engineering Contradiction:
ImproveperformanceVSAvoidplatform dependency
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a hybrid web application interface layer as an intermediary between the web application and the terminal system. This layer includes a system API processing unit that translates web-based API calls into platform-specific commands, enabling the application to access terminal resources (camera, GPS, accelerometer) while maintaining cross-platform compatibility. The interface layer acts as a mediator that resolves the conflict between native performance requirements and web-based platform independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a web application development method is used, then platform independence is improved, but terminal function control capability deteriorates

Engineering Contradiction:
Improveplatform independenceVSAvoidterminal function control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal interface layer that can operate across multiple platforms while providing access to platform-specific functions. The system API processing unit is designed to handle both web-based operations and native terminal control, making the application capable of functioning as a standard web application on some platforms and as a native-like application on others. This multi-functional design enables the same application code to adapt to different platform requirements without sacrificing terminal control capabilities.

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

3Productivity

If a hybrid web application structure is implemented, then development efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent divides the hybrid web application into distinct functional layers: a web user interface layer for standard web technologies, a hybrid web application interface layer for API processing and translation, and a cross-platform system service interface layer for terminal resource access. This segmentation allows each layer to be developed and maintained independently, reducing overall system complexity despite the multi-layered architecture. The modular structure enables developers to work on specific layers without affecting others, improving development efficiency while managing complexity through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8966508B2Method for executing hybrid web application and apparatus therefor
Publication Date: 2015.02.24 ELECTRONICS & TELECOMM RES INST
  • US8966508B2 patent drawing
  • US8966508B2 patent drawing
  • US8966508B2 patent drawing

AI summary

The device for executing a hybrid web application written in a web standard language including a system API call includes a web user interface layer that requests a process according to the system API call from a hybrid web application interface layer, and performs a process according to the web standard language, a hybrid web application interface layer that requests the process corresponding to the system API call from a cross platform system service interface layer in response to the request of the web user interface layer, receives a result of the process corresponding to the system API call from the cross platform system service interface layer, and transmits the received result to the web user interface layer, and a cross platform system service interface layer that performs a platform dependent operation corresponding to the system API based on the request of the hybrid web application interface layer.