Status flow improvements

[raladev]

Would be good to avoid not display confused statuses during installation/syncing/restarting processes.

• when xud container tries to get up on windows user can get no client status for xud -> would be good to change it to initializing...
• Syncing (0/0) status for lnd after container creation would be good to change to Connecting to peers orGetting block numbers
• During lnd wallet creation/unlocking process, lnd may get status that contain grpc err for 1-3 sec, would be good to prevet it too.

In general status flow should look like this without any error blinking:

xud:

Waiting for sync->Starting...->xud is locked->(if need some time to get ready stasus without any grpc error, we can add Unlocking... state)-> Ready

lnd:
Connecting to peers->Syncing(0/1234)->Waiting for wallet creation(if there is no wallet)/Waiting for unlock(if wallet was created before) -> Ready`

Connext:
Waiting for sync->Starting->Waiting for unlock->Ready

[kilrau]

I actually discussed exactly this with @peartobear this morning. My proposal is to have a completely different Initializing... experience and definitely do not want to iterate through red error states and messages. Not on create and not on start neither. Check the recording of yesterday's call to see what I mean.

Compare the different states of Umbrel

State 0: immediately after getting back to the dashboard after logging out

State 1: showing more details on the state after 30s-1min

Hence I believe, this is an xud-ui issue, not xud-docker-api.

Ready for your takeover ;) @peartobear

[peartobear]

The umbrel one is using a skeleton loading lib like https://github.com/dvtng/react-loading-skeleton which can be used if we can get logs from users another way. And we can get designers to build empty state for every screen using these skeletons, until data is available to populate the UI components. @kilrau @krrprr

[kilrau]

Please have a close look at the current messages the api exposes and see if you would want to change these. That's to be done in here, everything else -> new xud ui issue. @peartobear