Wow, thank you for the reward :D
My biggest issue with Raccoon, that was also an issue on other clients, is that if I close the app by going to the android home screen and then I reopen it again after some time, it doesn’t remember the post that was open. Another, possibly connected issue is that when returning from a post to the feed, it sometimes doesn’t remember the feed position and jumps to the top, reloading the feed. That would be okay if I reopened the app after a while, but Raccoon forgets the feed position rather quickly, and even when I don’t leave the app at all and just spend some time viewing the post, e.g. when writing comment on it.
Ok, that is an issue with state restoration (the lazy list state in the case of a feed which doesn’t retain the position). I will look into it and will catch the occasion to dive deeper in the question because, apart from state restoration for when the app goes into the background for a short amount of time, it is possible to save state in a persistent to survive even process termination (e.g. when the Android system kills an app which has been inactive for too long in the background but you reopen it from the task list).
Those things would be bread and butter in a normal app, unfortunately this is multiplatform which means that a lot of code is shared and platform-agnostic, so I have to investigate as how to correctly pass everything to the underlying native system. Thanks for the idea, it will be a nice learning path for me…
Thanks for mentioning this. I am quite annoyed that Android leave it to applications to handle restoration of killed apps. Palm OS released in 1996 did not have this problem. Every Palm OS apps would restore exactly to the state as when the task was closed.
Wow, thank you for the reward :D My biggest issue with Raccoon, that was also an issue on other clients, is that if I close the app by going to the android home screen and then I reopen it again after some time, it doesn’t remember the post that was open. Another, possibly connected issue is that when returning from a post to the feed, it sometimes doesn’t remember the feed position and jumps to the top, reloading the feed. That would be okay if I reopened the app after a while, but Raccoon forgets the feed position rather quickly, and even when I don’t leave the app at all and just spend some time viewing the post, e.g. when writing comment on it.
Ok, that is an issue with state restoration (the lazy list state in the case of a feed which doesn’t retain the position). I will look into it and will catch the occasion to dive deeper in the question because, apart from state restoration for when the app goes into the background for a short amount of time, it is possible to save state in a persistent to survive even process termination (e.g. when the Android system kills an app which has been inactive for too long in the background but you reopen it from the task list).
Those things would be bread and butter in a normal app, unfortunately this is multiplatform which means that a lot of code is shared and platform-agnostic, so I have to investigate as how to correctly pass everything to the underlying native system. Thanks for the idea, it will be a nice learning path for me…
Thanks for mentioning this. I am quite annoyed that Android leave it to applications to handle restoration of killed apps. Palm OS released in 1996 did not have this problem. Every Palm OS apps would restore exactly to the state as when the task was closed.