Application Model Integrating Web and Desktop Experiences

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current software applications either lack the security and control of traditional desktop applications or the ease of deployment and user experience of Web applications, with no effective solution bridging the gap between the two.

Innovation Solution

An Application Model that integrates the best features of Web and desktop applications, providing a secure framework for development, deployment, and maintenance, with elements for navigation, lifecycle management, and secure installation/update mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If Web applications are used, then ease of installation and deployment is improved, but security permissions and platform integration are worsened

Engineering Contradiction:

Improveease of installationVSAvoidsecurity permissions

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The application is segmented into web-based components that can be deployed independently through standard web hosting, eliminating the need for complex installation processes while maintaining security through the browser sandbox. Each functional module can be updated and deployed separately without affecting the entire application.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The web browser serves as an intermediary layer between the user and the application logic, providing secure execution environment while maintaining full platform integration capabilities. The browser sandbox ensures security permissions are enforced, yet the application can still access necessary system resources through approved interfaces.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If traditional desktop applications are used, then security permissions and platform integration are improved, but ease of installation and updates are worsened

Engineering Contradiction:

Improvesecurity permissionsVSAvoidease of deployment

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The application transitions from static desktop installation to dynamic web-based deployment, where the application can be updated, patched, and upgraded remotely without requiring user intervention or system administrator privileges. The deployment process adapts to different delivery scenarios (online/offline, initial install/updates).

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The application changes its deployment parameters from requiring full system integration and high installation overhead to using standard web protocols and minimal client-side requirements. Security parameters are maintained through browser-enforced sandboxes rather than operating system permissions.

Inventive Principle:

Principle #35Parameter changes

3Duration of action of stationary object

If traditional applications are installed, then offline capability is improved, but update management and system impact are worsened

Engineering Contradiction:

Improveoffline capabilityVSAvoidupdate management

Core Design Contradiction:

Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The application performs preliminary actions by downloading and caching necessary resources, data, and functionality to the client device before offline use is needed. This allows the application to function fully offline while maintaining centralized update management, as updates can be pushed to the cached application files without requiring reinstallation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The application serves multiple functions through a unified web-based architecture, providing both offline capability through local caching and centralized update management through web server communication. The same application instance can operate in offline mode while still being managed and updated through standard web protocols when connected.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of operation

If Web applications are used, then ease of navigation and user interface are improved, but execution permissions and platform capabilities are worsened

Engineering Contradiction:

Improvenavigation experienceVSAvoidexecution permissions

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The application replaces traditional mechanical execution permissions with web-based authorization mechanisms. Instead of relying on operating system security models, the application uses web protocols, authentication tokens, and browser security features to control access and capabilities, maintaining both user-friendly navigation and appropriate permission levels.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS8930944B2Application model that integrates the web experience with the traditional client application experience

Publication Date: 2015.01.06 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

This Application Model includes elements that define the scope of an application, its startup and shutdown behavior, and how it manages windows and resources; provide basic navigation functionality, journaling and journal extensibility, browser integration, and Structured Navigation; and define the way an application is deployed, installed, activated, updated, rolled back, and removed from the system in a secure, non-impactful way. It also enables using the same tools and languages for Web applications and locally installed applications, and allows the same application to be hosted in the browser or in a standalone window, based on a compile-time attribute.