Web Application State Transfer Between Lightweight and Classic Viewers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users navigating from a lightweight web application to a classic web application lose the current state of their operations and must reperform steps due to the lack of seamless transition between these applications, especially when the lightweight version lacks specific features.

Innovation Solution

A system that captures the state changes (delta) of the lightweight viewer before transitioning to the classic viewer, storing this delta in local browser storage, and applies it to the classic viewer to maintain the modified state without additional user input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a lightweight web application is used, then loading speed and resource consumption are improved, but functionality and available features deteriorate

Engineering Contradiction:

Improveloading speedVSAvoidfunctionality

Core Design Contradiction:

SpeedVSAdaptability or versatility

Solution Approach 1:

The web application is segmented into two versions: a lightweight version for fast loading and a classic version for full functionality. The system detects user navigation between these versions and selectively transfers state information, allowing each version to operate independently while maintaining continuity when needed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A state transfer mechanism acts as an intermediary between the lightweight and classic web application versions. This intermediary captures state changes in the lightweight version and selectively applies them when the user navigates to the classic version, enabling seamless transition without requiring full state synchronization.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a classic web application is used, then functionality and available features are improved, but loading speed and resource consumption deteriorate

Engineering Contradiction:

ImprovefunctionalityVSAvoidloading speed

Core Design Contradiction:

Adaptability or versatilityVSSpeed

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of transferring the complete state between application versions, the system performs partial action by selectively transferring only relevant state information (such as dashboard modifications, filter settings, or selected views) when navigation is detected. This reduces the overhead of state management while maintaining essential continuity.

Inventive Principle:

Principle #16Partial or excessive action

3Device complexity

If state is not maintained between applications, then device complexity and implementation difficulty are reduced, but user experience and operational efficiency deteriorate

Engineering Contradiction:

Improvesystem complexityVSAvoiduser experience

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The system performs preliminary action by detecting navigation events between application versions and proactively transferring relevant state information before the user completes their task. This automatic state transfer occurs in the background without requiring user intervention, maintaining simplicity while improving user experience.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by monitoring user navigation between lightweight and classic application versions and automatically adjusting state transfer based on detected navigation patterns. When navigation is detected, the system feeds back relevant state information to maintain continuity; when no navigation occurs, state transfer is minimized to maintain simplicity.

Inventive Principle:

Principle #23Feedback

4Ease of operation

If state transfer between applications is implemented, then user experience and operational efficiency are improved, but device complexity and implementation difficulty deteriorate

Engineering Contradiction:

Improveuser experienceVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS12547301B2Maintaining state between web applications

Publication Date: 2026.02.10 SAP SE

AI summary

State can be maintained between web applications such as a lightweight and a classic version of a web application. A lightweight viewer of a web application providing a visualization dashboard is run in a web browser. User inputs that modify the visualization dashboard are obtained. Then user input for navigation to a classic viewer of the web application is obtained. The classic viewer is navigated to in the web browser. Then the visualization dashboard of the classic viewer is modified to the modified state from the lightweight viewer without user input to the classic viewer.