4 ms·

Well, it works great if the apps aren't flushed -- but after an update about, I dunno, I wanna say 12 to 18 months ago, apps get terminated all the time (at lea

by dilap 4y ago

Well, it works great if the apps aren't flushed -- but after an update about, I dunno, I wanna say 12 to 18 months ago, apps get terminated all the time (at least on my iPhone 12). Since modern apps sort of expect not to be quit, they're generally quite bad about restoring state. Back in the early days of iOS it wasn't such a big deal -- apps expected to be quit and were good about restoring state. (This is a general problem with iOS itself too -- to use one salient example, pre-iOS 7, the phone was rock solid at remembering what you were listening too. Set your phone down, come back however much longer later, plug in the headsphones, hit the pause button on the headphones, whatever you were listening to starts right back up. Post iOS 7, not a chance. In general iOS 7 was just a dramatic downward plunge in software quality, and iOS has never recovered. Speaking of terrible software quality, now that I've reached 4 paragraphs, it's taking Safari maybe 1 second to echo each keystroke. So maybe some sort of quadratic algorithm processing text in this input box. Good lord.)

bombcar 4y ago
It has gotten insanely aggressive- I can have two apps total open and switching between them causes a clear and present reload.
dmitriid 4y ago
> Since modern apps sort of expect not to be quit, they're generally quite bad about restoring state. Which is also a recent development that includes Apple's own apps, too. iOS guidelines used to explicitly state that your app must expect to be terminated, and should restore state.
- dilap 4y ago
  Yep. Another example of this is scrolling views w/ buttons. Apple put out a whole whitepaper on how you have to take care to get this problem right: it's a subtle thing where you need to figure if the touch input is intended to be a scroll or a button tap. But after the latest redesign (a few years ago, now) "App Store" doesn't even get this right. Try scrolling around on the "Today" tab, picking various random points on the screen to scroll. You'll notice sometimes your scroll input is completely disregarded. Totally buggy. That's because if your touch starts on a button, you can't scroll. The button just steals it. Apple needs to read their own whitepaper! I don't know if it's just all the original people left or new leadership that doesn't have a feel for UI or what, but things are prettty rough. (I'm tempted to jump ship to Android/Linux, but despite Apple falling off, I know things will actually still be worse there. Unless a miracle has occurred.) Apple should hire me as Czar of Software Quality. ;-)
username223 4y ago
I’m glad I’m not the only one seeing these problems. App flushes have felt more aggressive and arbitrary, and apps are hit and miss for remembering state. Podcasts seems to be one of the worst for me, relaunching into the useless “listen now” state, or just hanging for 10 seconds before crashing. Apple really needs to spend a year just squashing bugs.
phist_mcgee 4y ago
People want battery life most of all. Aggressive app flushing is a part of that for the time being.
- dilap 4y ago
  Does an app staying resident in memory but suspended use battery tho? Also, I'd wonder if restarting an app wouldn't be more cpu (and thus battery) intensive than just unsuspending it.

by dilap 4y ago

bombcar 4y ago

It has gotten insanely aggressive- I can have two apps total open and switching between them causes a clear and present reload.

dmitriid 4y ago

> Since modern apps sort of expect not to be quit, they're generally quite bad about restoring state. Which is also a recent development that includes Apple's own apps, too. iOS guidelines used to explicitly state that your app must expect to be terminated, and should restore state.

dilap 4y ago
Yep. Another example of this is scrolling views w/ buttons. Apple put out a whole whitepaper on how you have to take care to get this problem right: it's a subtle thing where you need to figure if the touch input is intended to be a scroll or a button tap. But after the latest redesign (a few years ago, now) "App Store" doesn't even get this right. Try scrolling around on the "Today" tab, picking various random points on the screen to scroll. You'll notice sometimes your scroll input is completely disregarded. Totally buggy. That's because if your touch starts on a button, you can't scroll. The button just steals it. Apple needs to read their own whitepaper! I don't know if it's just all the original people left or new leadership that doesn't have a feel for UI or what, but things are prettty rough. (I'm tempted to jump ship to Android/Linux, but despite Apple falling off, I know things will actually still be worse there. Unless a miracle has occurred.) Apple should hire me as Czar of Software Quality. ;-)

username223 4y ago

I’m glad I’m not the only one seeing these problems. App flushes have felt more aggressive and arbitrary, and apps are hit and miss for remembering state. Podcasts seems to be one of the worst for me, relaunching into the useless “listen now” state, or just hanging for 10 seconds before crashing. Apple really needs to spend a year just squashing bugs.

phist_mcgee 4y ago

People want battery life most of all. Aggressive app flushing is a part of that for the time being.

dilap 4y ago
Does an app staying resident in memory but suspended use battery tho? Also, I'd wonder if restarting an app wouldn't be more cpu (and thus battery) intensive than just unsuspending it.