You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good interaction design states that there should be some visibility of system status.
The design should always inform users about what is going on through appropriate feedback within a reasonable amount of time.
Pallad users should, for example, be able to know the status of the wallet not just by seeing transactions populate in their transaction overview screen or when their balance changes but also when the wallet is querying data from the network. Should there be errors or challenges connecting to a web node, remote API provider, or local host, Pallad should communicate that to the user. One case is displaying errors to the user in an understandable way that limits the impact on the user experience or allows them to understand the system status with a low cognitive load (loading bars, icons, and colours can help significantly in this arena).
The text was updated successfully, but these errors were encountered:
Displaying Liveness of Pallad 🧟
Good interaction design states that there should be some visibility of system status.
Pallad users should, for example, be able to know the status of the wallet not just by seeing transactions populate in their transaction overview screen or when their balance changes but also when the wallet is querying data from the network. Should there be errors or challenges connecting to a web node, remote API provider, or local host, Pallad should communicate that to the user. One case is displaying errors to the user in an understandable way that limits the impact on the user experience or allows them to understand the system status with a low cognitive load (loading bars, icons, and colours can help significantly in this arena).
The text was updated successfully, but these errors were encountered: