Closed rfc2822 closed 7 months ago
@rfc2822
This leaves the question whether the spinner should shown while syncing? It's a bit too much in my opinion :)
Hmm the spinner was for service detection, right? Should we leave it as it is – progress bars for sync and spinners for detection? Or progress bars for everything including detection?
Idea: only progress bars, but when sync is initiated by swipe, show a snackbar
Spinners are more commonly used by Android apps, especially for the swipe down animation. That said, for AccountsActivity, progress bars for individual accounts works better than a single spinner.
So my suggestion would be: AccountsActivity: Swipe down triggers a snackbar which says that a sync for all accounts has been scheduled and the individual accounts all show a progressbar. No spinner.
AccountActivity: Always use a spinner. I would even go as far and say that the separation between update collections and sync is confusing, and you should always do both. This would make the UI simpler, as you would have a single sync button and you could drop the "Refresh address book list" menu entry.
Current plan:
Currently, the swipe-down gesture refreshes the collection list.
Suggestion: use swipe-down for sync instead. This would unify behavior with ICSx⁵ (later the Webcal subscriptions activity). Also, the gesture should do the "more common" operation, which is clearly sync.
For refreshing the collection list, there's still a secondary FAB + the menu entries.