search

btcpayserver / app

MIT License
5 stars 1 forks source link

Finalize the removal of the Getting Started section from the dashboard #66

Closed pavlenex closed 1 month ago

pavlenex commented 2 months ago

As we're moving things into settings, #44 we'll need space for balance chart so we should move remaining of the getting started steps

dstrukt commented 2 months ago

Small note for this one, the Getting Started section could be used for reminding the Owner to set up a Passcode, and/or users to configure a Backup, etc... Unless we're going to push this all into the onboarding flow at the beginning.

However, in the current state, agree, it makes sense to at least hide.

pavlenex commented 2 months ago

Why is passcode important? Could we use notification or something else? For backup we could prompt once there's fund in the wallet as per BDG https://bitcoin.design/guide/daily-spending-wallet/backup-and-recovery/cloud-backup/

cloud-backup-prompt@2x

dstrukt commented 2 months ago

Why is passcode important?

Security, no?

Could we use notification or something else?

For backup we could prompt once there's fund in the wallet as per BDG https://bitcoin.design/guide/daily-spending-wallet/backup-and-recovery/cloud-backup/

Similar to the back-up, I think it just depends where we want to inject it into the app. Both the passcode or back-up aren't "necessary", and can easily be accessed after initial configuration in the settings views, but this is more tucked away and we're not actively promoting best practices with this.

We have a chance to be more opinionated and push people to set up these things before they take any action (which is the more prudent, but i see both sides of doing it after you have something to lose, so you'll care more)... or have it be a persistent non-invasive reminder via the Dashboard (Owner) or Settings (Employee) view.

As IMO the drawback of the BDG's drawer UX pattern is this might only appear once, otherwise, it's an annoying persistent drawer (triggered every time) that requires an additional click to dismiss, or until you take the action - both forms are not ideal from my POV, especially the former if you do indeed have to do it "Later", as it just becomes a 1 time reminder that then becomes tucked away in the settings, but I suppose it's better than nothing... Not to mention it could be missed entirely if your app doesn't follow the more standard send/receive wallet flow and the user clicks on the transaction detail view, in this example :shrug:

But opinions aside, where would this drawer be triggered in our flows? Can save that for the next call.

Otherwise, the passcode/cloud back-up is the standard wizard format, regardless of how or where it's triggered.

dstrukt commented 1 month ago

Going to close this and open a specific issue for Back-ups, as we have an Issue for Send flows specifically as well now.