Web Application Desktop Integration via Boundary Definition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face challenges in integrating web applications with their desktop environment due to difficulties in defining website boundaries and the dual boot problem, where browsers provide distractions, making it hard to concentrate on specific tasks.

Innovation Solution

A mechanism allowing developers to define user interaction boundaries using client-side code, enforced by a run-time engine, enabling features like start menu shortcuts, jumplist integration, and navigation within a web application mode browser that minimizes browser distractions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If end-users define website boundaries through client-side script, then desktop integration is achieved, but user experience breaks due to lack of knowledge about website construction

Engineering Contradiction:
Improvedesktop integrationVSAvoiduser experience
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a website boundary definition mechanism that acts as an intermediary between the website and the user's desktop integration. The website can define its boundaries through structured data (such as manifest files or metadata) that the desktop environment reads to determine integration scope. This eliminates the need for end-users to write client-side scripts while maintaining reliable user experience, as the boundary definition is handled by the website owner through standardized mechanisms rather than ad-hoc user scripting.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If users boot their personal computers and start browsers to launch web applications, then web applications can be accessed, but distractions in browser chrome prevent task concentration

Engineering Contradiction:
Improveweb application accessVSAvoidbrowser distractions
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent enables web applications to be extracted from the full browser environment and launched as standalone desktop applications. When a user pins or installs a web application to the desktop, it launches in a dedicated window without the full browser chrome (address bars, tabs, extensions, etc.), providing a distraction-free experience while maintaining access to the web application functionality. This extraction principle allows users to access web applications directly from the desktop without booting the full browser environment.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If browsers provide full functionality, then web applications can be fully accessed, but too many distractions appear in browser chrome

Engineering Contradiction:
Improveweb application functionalityVSAvoidbrowser interface
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by providing different interface qualities for different usage contexts. When a web application runs in the full browser, it has access to complete browser functionality. When pinned or installed as a desktop application, it runs in a simplified window with reduced chrome and interface elements. This allows the same web application to adapt its interface complexity based on how it is launched, providing full functionality when needed while reducing distractions for focused tasks.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP2580683B1Creating and launching a web application with credentials
Publication Date: 2018.04.25 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2580683B1 patent drawingFigure 1
  • EP2580683B1 patent drawingFigure 2
  • EP2580683B1 patent drawingFigure 3

AI summary

Various embodiments provide a mechanism to allow end users to install web applications and websites onto their desktop. In accordance with one or more embodiments, client-side code can be utilized to allow developers associated with a website to define boundaries associated with user interaction, and have those boundaries enforced by a run-time engine. In at least some embodiments, developers can provide, through JavaScript code and/or HTML markup, various configurations for the creation of a start menu shortcut, navigation, and so-called jumplist integration.