Problem: (Tested on 2.8.0) When leaving the app opened in the background for a while, the memory manager might kill it, and after returning to it all state is lost, you go back to the home page, and loses whatever thread you had open.
Background: After some getting used to the new design, which I've grown to enjoy, I noticed I am constantly losing my threads. It's very common for me to leave a thread open to read later, when I have to do something else for a while.
I was used to leaving it open for hours, coming back to it from time to time. But now this is not possible.
I am not sure if this is because the new design consumes more memory, or the old one saved state when getting killed.
Regardless, I think this is a good practice to any app, and it would benefit a lot from doing.
A few years ago I was an Android dev, so I wish I could contribute this myself. But I have no Flutter tools nor knowledge to figure it out now.
Anyways, great app! Thanks for it.
Problem: (Tested on 2.8.0) When leaving the app opened in the background for a while, the memory manager might kill it, and after returning to it all state is lost, you go back to the home page, and loses whatever thread you had open.
Background: After some getting used to the new design, which I've grown to enjoy, I noticed I am constantly losing my threads. It's very common for me to leave a thread open to read later, when I have to do something else for a while.
I was used to leaving it open for hours, coming back to it from time to time. But now this is not possible.
I am not sure if this is because the new design consumes more memory, or the old one saved state when getting killed.
Regardless, I think this is a good practice to any app, and it would benefit a lot from doing.
A few years ago I was an Android dev, so I wish I could contribute this myself. But I have no Flutter tools nor knowledge to figure it out now.
Anyways, great app! Thanks for it.