4 ms·
It used to be extremely common to allow users to select features at install time, mostly in order to save disk space. It’s not particularly common any more, and
by chrismorgan 6y ago
It used to be extremely common to allow users to select features at install time, mostly in order to save disk space. It’s not particularly common any more, and I don’t think any app stores support the concept.
Deactivating features based on battery life? That’s absolutely still a thing on native apps. If you throw Windows into battery saver mode, for example, the acrylic material becomes opaque; if you put Android into power saver mode, native controls will shut off their gratuitous animations, things like that. Nothing major, but a bunch of small things.
- paulryanrogers 6y agoIt may be coming back. Latest Call of Duty has a lighter install option. And Fortnite is getting a lighter version as well.
- theamk 6y agoNote that’s a mode which needs to be explicitly activated by user, and the user is aware of. This is fine. The post offers something else: vague heuristics, different on each website, and no feedback or ways to override. See the difference?
- chrismorgan 6y agoI agree that it’s an important distinction, and disk space saving things are seldom automatic (but not never); but power saving mode is routinely activated without user input, e.g. Windows defaults to switching into it at 20%.
- madeofpalk 6y ago> I don’t think any app stores support the concept At least the iOS App Store I believe supports splitting up assets and loading them after initial install (optionally?)
- tored 6y agoI have a crazy idea, lets code as if we were always on battery saving mode. ¯\_(ツ)_/¯
- SGML_ROCKSTAR 6y agoI'd like to read what you have to say about doing so.
- tored 6y agoIf features doesn't need to be loaded, are they actually needed?
- SGML_ROCKSTAR 6y agoLoading them being unnecessary would be so when? Do you have time to elaborate?