eloquence
commented
4 years ago Before we can consider this dev-ready, I think we should resolve the following questions:
1) Do we want to keep user-initiated syncs around at all?
2) What events should trigger this animation? Only user syncs (provided we keep them), or background syncs as well? How about user-initiated downloads or other network operations? Note that downloads currently add a "Downloading file" status update to this same area of the client, so we're already overloading it semantically beyond syncs.
3) For a sync, should the animation only last for the duration of the initial "is there anything new" check, or until all messages and replies associated with it have been downloaded?
Back in July, Nina created this spreadsheet which conveys a set of proposals for how the icon and status message should be updated based on user actions, and which proposes answers to some (but not all) of these questions.
For the beta, I would encourage us to look for ways to dramatically reduce complexity here. Here's a proposal:
- Eliminate user-initated syncs entirely.
- Animate the icon during syncs, including any message/reply downloads associated with a sync.
- Don't animate the icon or update the status for other user-initiated actions. Instead, show such operations in context as we've already started doing with replies.
In other words, treat it as the "sync progress area", not the "all network activity reported here" area. Even in that context, we might want to not animate the icon during the "is there anything new" stage of the sync, if we perform this check constantly, because that could get very visually annoying and distracting.
redshiftzero
ninavizz
Description
When a user clicks on the refresh icon, we display the refresh_active icon. This should be animated ("rotating at a pleasingly elegant pace... nothing frenetic or sluggy")