Re:These are called opportunities
by carlmr on Thursday December 03, 2020 @01:48AM
(#25286225)
For productivity apps I could see this working, but this would be the death of e.g. phone games, VR experiences etc.
Some things just take a lot of power to compute.
The issue I see is that it's kind of hard to measure whether the app needs this much CPU or if it's a bad design.
Aligning these incentives is obviously necessary. But it's not such an easy problem.
You'd have to start categorizing apps by how fast they should be (e.g. calendars should start in < 0.5 seconds and use at most 3% CPU on average). Then you may be able to align incentives this way. However then the problem becomes categorizing your apps and having useful categories for everything. Then maybe somebody has an idea for an AI calendar that needs more CPU, but is a lot more useful, because it can predict a host of events. Now they can't upload that to the app store.
Some things just take a lot of power to compute.
The issue I see is that it's kind of hard to measure whether the app needs this much CPU or if it's a bad design.
Aligning these incentives is obviously necessary. But it's not such an easy problem.
You'd have to start categorizing apps by how fast they should be (e.g. calendars should start in < 0.5 seconds and use at most 3% CPU on average). Then you may be able to align incentives this way. However then the problem becomes categorizing your apps and having useful categories for everything. Then maybe somebody has an idea for an AI calendar that needs more CPU, but is a lot more useful, because it can predict a host of events. Now they can't upload that to the app store.