Browser Presence Indicators for Shared Content Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In content management systems, users face versioning conflicts and lack awareness of others' interactions with shared content items, leading to unintended modifications due to parallel editing without real-time feedback.

Innovation Solution

A client application monitors interactions with shared content items, providing users with real-time presence information and notification features, allowing them to view and communicate changes across devices, and managing synchronization to prevent conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple users edit shared content items in parallel without real-time feedback, then user productivity and collaboration speed are improved, but versioning conflicts and data loss occur

Engineering Contradiction:
Improvecollaboration speedVSAvoidversioning consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements real-time feedback by monitoring presence information from multiple devices and notifying users when others are viewing or editing shared content items. This feedback loop allows users to adjust their editing behavior accordingly, preventing versioning conflicts while maintaining parallel collaboration capabilities.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The client application acts as an intermediary between the native application and the content management system. It monitors interactions, collects presence information, and communicates status to other devices, mediating between parallel editing actions and conflict prevention without hindering productivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If users are notified in real-time about others' interactions with shared content, then versioning conflicts are reduced, but system complexity and processing overhead increase

Engineering Contradiction:
Improveversioning consistencyVSAvoidclient application complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the monitoring and notification functionality into a separate client application that operates independently from the native application. This segmentation allows the native application to maintain its simplicity while the client application handles the complexity of presence monitoring and conflict prevention.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The client application automatically monitors presence information and manages notification logic without requiring user intervention. It self-manages the complexity of tracking multiple devices, interpreting presence states, and coordinating edits, reducing the perceived complexity for end users.

Inventive Principle:
Principle #25Self-service

3Loss of information

If presence information is continuously monitored and displayed, then user awareness of others' interactions is improved, but energy consumption and processing resources increase

Engineering Contradiction:
Improveawareness of interactionsVSAvoiddevice energy consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

Instead of continuous monitoring, the system uses periodic presence information updates triggered by specific events (e.g., when a user opens, edits, or closes a content item). This periodic action maintains user awareness while significantly reducing energy consumption compared to continuous real-time monitoring.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The client application pre-registers for presence information events and sets up monitoring beforehand. This preliminary action allows the system to efficiently wait for and respond to relevant events without requiring continuous active processing, thereby conserving energy while maintaining awareness.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11683389B2Browser display of native application presence and interaction data
Publication Date: 2023.06.20 DROPBOX INC
  • US11683389B2 patent drawing
  • US11683389B2 patent drawing
  • US11683389B2 patent drawing

AI summary

A client application of a device receives presence information and other interaction information from other devices synchronized to a set of content items. The interaction information indicates interactions of at least one other device with respect to a synchronized content item. The client application displays a browser depicting the synchronized content items and permitting navigation among organizational elements. The browser also displays the interaction information associated with the content items received from the other devices. The browser displays the interaction information with respect to particular content items or for an organizational element. The browser may also include an activity feed displaying interaction information specific to a content item or relating to a synchronized folder or organizational element. This permits a user to view, at a browser, activity and interactions of other users with respect to content items using native applications on another device.