Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

Overhaul Sync + Status to be ✨ Delightful ✨ #230

Closed
3 of 10 tasks
DanGould opened this issue Oct 26, 2021 · 1 comment
Closed
3 of 10 tasks

Overhaul Sync + Status to be ✨ Delightful ✨ #230

DanGould opened this issue Oct 26, 2021 · 1 comment

Comments

@DanGould
Copy link
Member

DanGould commented Oct 26, 2021

It's front & center UX. We can make onboarding easier and the experience more delightful.

  • make people know it's synchronizing 🧯 privately in UI
  • Don't show synced only if FiltersLeft == 0 cause that's the default state for the int. Connection & filters DL'd & processed
  • "[Privately] Sync'd to " based on most recently processed filter, not just downloaded. Filters have unixtime
  • $ 11.6 Include update checker #62 include update checker UI i.e. if backend hardforks tell user to update in UI
  • collapse vertically. It's 5 lines right now :O. Perhaps only display the sync item that ought to happen yet (Tor starting -> Backend connected -> Synced to x [height] -> full node unreachable -> seeking Bitcoin peers -> [show nothing if everything is connected]
  • Integrate full node connection status if it's behaving unexpectedly Connect Full Node UI #217
  • Sync from wallet creation height Sync new wallet from server block height #159 sync from recent height on new wallet #196 Feat/sync new from now (subrepo) #232
  • Update the status on background. I think this can be done by making the status component transient. Right now it's a singleton and when you resume from the background it says connected cause it doesn't receive any update events in the background and the most recent event was being connected
  • Get tor status (& progress) from TorManager instead of through Synchronizer pipeline
  • Don't "process filters" from 0 every time the wallet opens. That messes the balance up and scares folks. Right now we cache Balance in the UiConfig & UI until this processing is done but still occasionally have problems
@DanGould
Copy link
Member Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant