Hybrid App Offline Access via Native Layer Segmentation

Solution Overview

Problem

Web-based systems have limitations, such as requiring a constant internet connection for content creation and restricted interactions and data storage on user devices, making it burdensome to replicate their functions with native client-side code.

Innovation Solution

A hybrid client application is developed, comprising a native layer and a web view, allowing offline operation by loading resource bundles from local storage, which include web code for GUI presentation and server communication, enabling access to native device features and web client functionalities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a web client is used to access content creation features, then ease of operation is improved, but offline access capability deteriorates

Engineering Contradiction:

Improveease of operationVSAvoidoffline access capability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The application is divided into two distinct layers: a native layer that provides offline access capabilities and device-specific functionality, and a web view layer that provides the familiar web client interface. This segmentation allows each layer to specialize in its strengths while working together to resolve the contradiction between ease of operation and offline access capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent merges the advantages of native applications (offline access, device integration) with the advantages of web applications (ease of operation, cross-platform compatibility) into a hybrid architecture. The web view is embedded within the native layer, creating a unified application that combines both paradigms to simultaneously achieve ease of operation and offline access capability.

Inventive Principle:

Principle #5Merging (Combining)

2Reliability

If native client code is written to replicate web client functions, then offline access capability is improved, but device complexity increases

Engineering Contradiction:

Improveoffline access capabilityVSAvoiddevice complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The application is divided into two distinct layers: a native layer that provides offline access capabilities and device-specific functionality, and a web view layer that provides the familiar web client interface. This segmentation allows each layer to specialize in its strengths while working together to resolve the contradiction between ease of operation and offline access capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The native layer serves multiple functions: it provides offline access to content, manages local storage, interfaces with device-specific features, and hosts the web view. This multi-functionality reduces the need for separate components, thereby managing device complexity while maintaining offline access capability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of manufacture

If web client code is used for content creation, then ease of manufacture is improved, but offline functionality deteriorates

Engineering Contradiction:

Improveease of manufactureVSAvoidoffline functionality

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The application is divided into two distinct layers: a native layer that provides offline access capabilities and device-specific functionality, and a web view layer that provides the familiar web client interface. This segmentation allows each layer to specialize in its strengths while working together to resolve the contradiction between ease of operation and offline access capability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The native layer pre-loads and caches content locally on the user's device before offline access is needed. This preliminary action ensures that content is available offline without requiring complex offline-specific code, maintaining ease of manufacture while enabling offline functionality.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11740891B2Providing access to a hybrid application offline

Publication Date: 2023.08.29 DROPBOX INC

AI summary

Disclosed are systems, methods, and non-transitory computer-readable storage media for providing access to a hybrid web application offline. In some implementations, a computing device can be configured with a hybrid application that includes a native layer and a web view. The native layer can provide access to native features of the computing device while the web view can provide web client features, such as graphical user interfaces and server communication functionality. When the computing device is offline and the hybrid application is invoked, the native layer can load from local storage a resource bundle including the web code needed to present the web view graphical user interface, and/or facilitate communication with the web server. Similarly, when the computing device is offline, the hybrid application can load previously stored content items into the web view from local storage through the native layer so that the user can work with the content items offline.