Just had a (very rare) crash in the Android app, and discovered that the long article I’d been in the middle of had already been marked as read when I restarted. In this instance I could relocate it but that’s not always easy. I wonder would it be possible to queue up the mark-article-as-read action for the moment that the reader moves on, whether by swiping to the next article, exiting to the articles list, etc., so that crashes don’t result in articles prematurely being marked as read?
1 Like
[Just to be clear: I’m not talking about changing the rules of what constitutes “reading” an article, just the point in time at which those rules get applied.]