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…