Pull-down bookmarks/history lists to trigger sync
Issue :- #2165
Why is it a problem?
As a user I would like to sync items swiftly.
How would you solve the problem? What is your design proposal?
The gesture to pull-down to sync seems intuitive and swift to me. Here, I'd like to put up the UI for syncing various items like bookmarks and history lists etc. I feel like as I mentioned in the issue #80, the pull down gesture on websites should refresh the web page, whereas, for other screens like homescreen, bookmarks list, and history, it should perform the task to sync them.
For the homepage, the opened tabs and all the other collections which are not yet synced should get synced.
For the bookmarks, the bookmarks which are not yet synced should get synced.
For the history list, the history which are not yet synced should get synced.
And so on and so forth for the other screens which ask for the feature of getting synced.
One more design exploration that I got an idea about is, whether or not to show a user if an item is synced or not. I feel like it should be and I have involved a UI solution for this as well below.
How would you measure your designs effectiveness?
Analytics as to how much the sync API is called/triggered through this pull-down feature vs through following the normal progressive steps to sync an item.
What is the problem you are trying to solve?
Pull-down bookmarks/history lists to trigger sync Issue :- #2165
Why is it a problem?
As a user I would like to sync items swiftly.
How would you solve the problem? What is your design proposal?
The gesture to pull-down to sync seems intuitive and swift to me. Here, I'd like to put up the UI for syncing various items like bookmarks and history lists etc. I feel like as I mentioned in the issue #80, the pull down gesture on websites should refresh the web page, whereas, for other screens like homescreen, bookmarks list, and history, it should perform the task to sync them. For the homepage, the opened tabs and all the other collections which are not yet synced should get synced. For the bookmarks, the bookmarks which are not yet synced should get synced. For the history list, the history which are not yet synced should get synced. And so on and so forth for the other screens which ask for the feature of getting synced.
One more design exploration that I got an idea about is, whether or not to show a user if an item is synced or not. I feel like it should be and I have involved a UI solution for this as well below.
How would you measure your designs effectiveness?
Analytics as to how much the sync API is called/triggered through this pull-down feature vs through following the normal progressive steps to sync an item.