zlacker

>If you are in the middle of typing a comment and switch to another app, when you come back, it will reload the display, losing your comment.

This is the rule for a lot of apps and mobile websites now. I don't understand why - we have so much RAM available - but they love to refresh whether there's a reason to or not. And even if there's a reason not to. I can't count the number of times I've tapped on a tab that has a minature version of all the information I want, only for it to be replaced by a loading screen or 404.

A while ago I noticed my battery usage had gone way up. It was because any time I was distracted from my phone (or lost internet connection on a train), I would just leave the display on. Locking the phone meant that I'd lose whatever context I had.

>>devnul+(OP)
> I don't understand why - we have so much RAM available

It’s not even that. There are APIs to persist state beyond app termination. Even if your app gets killed due to memory pressure, it should continue where it left off.

>>devnul+(OP)
It's probably refreshing because iOS is aggressive about killing websockets, even if you only backgrounded safari for a few seconds. And it's easier to do a reload than determine which messages were missed. It's hard to even tell if the websocket is dead since it just stays open but is unable to receive / send messages.

Or at least this was my experience working on a mobile PWA a few years ago. I don't even own an apple device, it's just the ios bugs were always the most painful / memorable.