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
When using the app, the history is most useful when it allows a "quick glance" of the past activities. For this to work well, it should load as fast as possible. However, when the app is opened now, it takes a second or two - sometimes even longer - for any items to appear.
This is likely to get worse when more activities are fetched for the list of
Solution
Show an indicator that loading is happening, but complement this by showing a cached version of the list that was loaded when the app was previously launched.
Details
I would like to do this by abstracting and improving the entire ChildObserver-logic. The class has grown overly complicated, but could easily do this b breaking it into abstract submodules. Kind of a lot of work but should pay off big time down the line.
The text was updated successfully, but these errors were encountered:
Problem
When using the app, the history is most useful when it allows a "quick glance" of the past activities. For this to work well, it should load as fast as possible. However, when the app is opened now, it takes a second or two - sometimes even longer - for any items to appear.
This is likely to get worse when more activities are fetched for the list of
Solution
Show an indicator that loading is happening, but complement this by showing a cached version of the list that was loaded when the app was previously launched.
Details
I would like to do this by abstracting and improving the entire ChildObserver-logic. The class has grown overly complicated, but could easily do this b breaking it into abstract submodules. Kind of a lot of work but should pay off big time down the line.
The text was updated successfully, but these errors were encountered: