lbryio / lbryio/lbry-desktop

offline mode when can't connect to sdk / internet

Open
#2,181 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: ux help wanted level: 3 priority: medium type: new feature
Dominant language
JavaScript
Stars
3.5k
Forks
409
PR merge metrics
No merged PRs in 30d

Description

## The Issue
We should allow the app to startup without a SDK connection in "offline mode". With numerous planned upgrades to the SDK, there may be times when an upgrade affects a large set of app users where they can't startup. If we allowed offline mode, they could at least startup and grab an update we would have pushed, otherwise, they need to manually download/install. Offline mode would also allow users to watch their downloaded content (probably needs file_list caching first).

## System Configuration

- LBRY Daemon version:
- LBRY App version:
- LBRY Installation ID:
- Operating system:

## Anything Else

## Screenshots

## Internal Use

### Acceptance Criteria
1.
2.
3.

### Definition of Done
- [ ] Tested against acceptance criteria
- [ ] Tested against the assumptions of the user story
- [ ] The project builds without errors
- [ ] Unit tests are written and passing
- [ ] Tests on devices/browsers listed in the issue have passed
- [ ] QA performed & issues resolved
- [ ] Refactoring completed
- [ ] Any configuration or build changes documented
- [ ] Documentation updated
- [ ] Peer Code Review performed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing the app startup path and SDK connection handling; define the offline behavior around starting without an SDK connection, updating the app, and watching downloaded content, including the proposed file_list caching. Done means the app can start offline and support the stated recovery and playback use cases, with tests covering the acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.