Thanks, that makes sense. Automatic background refresh sounds much better from a wallet UX perspective. The part I would still worry about is failure visibility. If the refresh process fails because of connectivity, relay issues, liquidity conditions, or implementation bugs, the wallet probably needs to make that very obvious to the user. Since the solutions are still early, I imagine good warnings and safe fallback behavior will be almost as important as the automation itself. It will be interesting to see which approach eventually becomes the common pattern.
Thanks, that makes sense. Automatic background refresh sounds much better from a wallet UX perspective. The part I would still worry about is failure visibility. If the refresh process fails because of connectivity, relay issues, liquidity conditions, or implementation bugs, the wallet probably needs to make that very obvious to the user. Since the solutions are still early, I imagine good warnings and safe fallback behavior will be almost as important as the automation itself. It will be interesting to see which approach eventually becomes the common pattern.