Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Briar Desktop Briar Desktop
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • Briar DesktopBriar Desktop
  • Issues
  • #98

Closed
Open
Created Oct 28, 2021 by Mikolai Gütschow@ialokimMaintainer

Move Briar API calls to background thread

While the Briar API calls will now be logically separated from the UI thanks to the view models (!33 (merged) and !34 (merged)), all the calls are still executed on the main (UI) thread.

In the Android app, all those calls are run on a dedicated database thread (see, for example, here).

We should use a similar approach, but we can take advantage of the nice Kotlin coroutines approach, that allows to run coroutines on a different IO thread (pool?).

Assignee
Assign to
Time tracking