3 ms·
> This would require significant extra work in just about every app, 2x as much in some, probably averaging around 1.5x as much in most. That is not a reasonabl
by Dylan16807 4y ago
> This would require significant extra work in just about every app, 2x as much in some, probably averaging around 1.5x as much in most. That is not a reasonable expectation.
This is not a reasonable estimate of the work needed.
Also I was thinking more of "don't waste tons of memory, making it unable to run on devices with less", which could just be a mandatory rule for everyone's benefit.
- throwanem 4y ago> This is not a reasonable estimate of the work needed. One of the things that did the most to change my mind on this subject was actually estimating that work - specifically, estimating what it'd take in a live and fairly complex app, which is where most teams would have to start. (You haven't lived till you've tried to prototype a complicated custom time series chart control with several interactions, that can transparently render itself across a wide range of sizes and be legible and usable in all of them. You really haven't lived till you've tried to test it!) Another was seeing for myself in Amplitude both the absolute fraction and the trend for how few users would even be in a position to notice the result. > Also I was thinking more of "don't waste tons of memory, making it unable to run on devices with less", which could just be a mandatory rule for everyone's benefit. I agree this is worth more than it's valued. Would such a singleminded focus be to everyone's benefit, though? Most apps might not spend much effort on clean UI restore after suspend, but actual data loss is very rare in my experience, and teams have only the capacity that they do. That makes it a tradeoff between features and other bugfixes, and this; the next request I see in Canny for showing the launch screen less often on app switch will be the first, an absence which likewise leads me to suspect that the wants of users in general aren't accurately captured in the perspective of those who are heavily invested on this point.
- theshrike79 4y agoBut where does the line between "wasting memory and resources" and "wanting to make a game that utilises the full power of a modern phone" go? It's REALLY hard to make a game that works equally well on the latest and greatest and also that one weird Android phone someone in the Philippines bought in an outdoor market.
- Dylan16807 4y agoIf you're truly using that power, and can't just turn down the graphics, that's fine. The complaint is when boring apps like the train ticket handler start running out of memory at random. A huge majority of non-game apps could fit into a small amount of resources if the devs tried.