Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UC] Offline Support / Local-First #96

Open
Laurin-W opened this issue Jan 13, 2025 · 0 comments
Open

[UC] Offline Support / Local-First #96

Laurin-W opened this issue Jan 13, 2025 · 0 comments
Labels
needs-discussion This use-case or issue will be added to the agenda and discussed in the LWS meeting. triage Issues needing triage usecase LWS Use Case

Comments

@Laurin-W
Copy link

As a user,
I want to use resources offline or with an unstable connection without running into data inconsitencies.
So that my UX is not disrupted and I don't have to resolve sync conflicts .

Preconditions:

n/a

Trigger:

  • User reads or modifies a resource. The application has a bad or no connection to the internet.
  • Two actors manipulate the same resources simultaneously.

Actors:

  • user
  • application
  • storage provider (running on local device)

Distinction:

  • Conflict Resolution (CRDT)
  • Local device needs to sync parts or all of the data with replicas
  • Challenge: The device is offline and wants to create or manipulate resources
    • HTTP identifiers are issued by remote server (not acccessible)
      • Alternative: A local service manages the LWS resources; another URI scheme becomes necessary
    • Resources need to be preloaded on the device

Scenario:

User does not notice if offline or online. Changes to a resource by other actors are seemless.

Alternative case(s):

n/a

Error scenario:

  • A resource is edited in multiple places (or by multiple users) and upon synchronization, there are conflicts that need to be resolved. A manual resolution is going to be a UX failure.
  • A resource is created (with a unique identity) or requested but the address resolution fails.

Acceptance Criteria:

  • The user can use LWS apps without internet connection.
  • There are no inconsistencies

References:

@Laurin-W Laurin-W added triage Issues needing triage usecase LWS Use Case labels Jan 13, 2025
@hzbarcea hzbarcea added the needs-discussion This use-case or issue will be added to the agenda and discussed in the LWS meeting. label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-discussion This use-case or issue will be added to the agenda and discussed in the LWS meeting. triage Issues needing triage usecase LWS Use Case
Projects
None yet
Development

No branches or pull requests

2 participants