Content reloads every time when switching between App-tabs

[tclaus]

When I switch between "Stream" and a tab - lets say "Mail" and back - content reloads always.

A content caching between switching would be nice - user can swipe down to reload every time.
Invalidate cache after a period of time, maybe 1 minute or so.

Bonus: If parts of the stream is cached - update the cache with new content. Currently the screen gets black while reloading.
(It's just an eye candy, but let the client look really cool)

[jhass]

Yes, for now always reloading made sure users don't need to know how to manually reload, but of course that's just the simplest solution to the UX problem.

Another simple approach could be to show cached content when available but also always reload in the background. It's just really hard to then update with the new content without jumpy UI and the user noticing that they could scroll up to newer content now. Maybe we should inverse stream order....

I've also been considering to track the scroll position (as in last visible post) and restoring to that, inserting new content in the background above it. But it's a really hard problem, even harder than just caching. Especially since diaspora's paging API isn't really designed with that in mind, so it would need at least two requests to discover if there's new content since the remembered post, usually a lot more and thus degrading pod and client performance a lot.

[tclaus]

Cool ideas making background updates. Maybe a step-by-step approach has lower hurdles and same quick wins.

[tclaus]

On every tab switch- the view is disposed and new created.
Maybe this is an even quicker win, if the view is persistent between tab switches?
(My known apps on iOS do so)

[jhass]

Mmh, how to avoid running out of memory then? More importantly I'd like to preserve current navigation behavior however, that is every item in the bottom navigation is "top-level" and empties the navigation stack, meaning going back from a "top-level" screen leaves the app.

So if you find a way that frees up memory when it comes under pressure and preserves the current navigation hierarchy, sure :)