Hybrid Mobile App Controller for Cross-Platform Resource Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional client applications built using HTML and JavaScript face limitations in accessing local resources on mobile platforms, while native SDK approaches are not scalable across different platforms, requiring separate app versions for each platform.

Innovation Solution

A hybrid approach that combines HTML and native SDK to build mobile applications, allowing access to platform-specific resources through a unified User Interface (UI) that invokes both remote and native operations, using an application controller to manage and execute operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If HTML+JavaScript is used to build client applications, then the app is easy to update and can run on any platform, but the app cannot access local resources on mobile platforms

Engineering Contradiction:
Improveplatform compatibilityVSAvoidinability to access local resources
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The patent combines HTML+JavaScript with native SDK capabilities into a hybrid application model. The HTML app runs in a web view while a native bridge enables access to local resources through native operations, merging the cross-platform benefits of HTML with the resource access capabilities of native apps.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces a native bridge as an intermediary component that connects the HTML+JavaScript application layer with the native operating system resources. This bridge translates HTML app requests into native operations, enabling indirect access to local resources without requiring the entire app to be native.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-generated harmful factors

If native SDK is used to build client applications, then the app can access local resources on the platform, but it requires separate app versions for each platform

Engineering Contradiction:
Improveaccess to local resourcesVSAvoidmultiple platform versions
Core Design Contradiction:
Object-generated harmful factorsVSDevice complexity

Solution Approach 1:

The patent creates a universal HTML+JavaScript codebase that can run on multiple platforms through the web view. The same HTML app can access local resources on different platforms by invoking platform-specific native operations through the native bridge, eliminating the need for separate native app versions for each platform.

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

Solution Approach 2:

The patent segments the application into two independent layers: a universal HTML+JavaScript layer that handles cross-platform logic and UI, and a platform-specific native bridge layer that handles resource access. This segmentation allows the HTML layer to remain unchanged across platforms while the native bridge adapts to each platform's specific resources.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If a hybrid approach combining HTML and native SDK is used, then access to local resources is enabled with unified UI, but the system complexity increases

Engineering Contradiction:
Improveresource access capabilityVSAvoidsystem architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The native bridge serves as a thin intermediary layer that adds minimal complexity while enabling resource access. It provides a standardized interface for the HTML app to request native operations, translating these requests into platform-specific calls without requiring complex integration logic in the HTML layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a feedback mechanism where the native bridge monitors and manages the interaction between HTML operations and native resources. This feedback loop ensures proper resource management, error handling, and state synchronization, reducing the complexity of managing hybrid application state.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2946574B1Systems and methods for building and using hybrid mobile applications
Publication Date: 2017.08.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2946574B1 patent drawingFigure 1
  • EP2946574B1 patent drawingFigure 2
  • EP2946574B1 patent drawingFigure 3

AI summary

Systems and techniques of building and presenting hybrid remote client applications for and to users of a mobile device are presented. Upon a user accessing a remote client application, the mobile device may launch a unified User Interface (UI) that provides the user with a list of allowable operations associated with the remote client application. Such allowable operations may include JavaScript operations that are supplied by the remote client application - e.g., via a HTML web page. In addition, an allowable operation may include a native operation that is supplied by the native SDK of the mobile device.