4 ms·
This is tough. On one hand, there's obviously a demand (of which I am part) for f.lux, but on the other, 15 million downloads, despite being a respectably big n
by mortenjorck 11y ago
This is tough. On one hand, there's obviously a demand (of which I am part) for f.lux, but on the other, 15 million downloads, despite being a respectably big number, barely registers compared to an install base that can grow by 75 million in a single quarter. Using private APIs does negatively impact the iPhone experience (witness the constant screen wakes in the pulled Xcodeproj), and making those APIs public has development overhead – As big as the iOS team may be, its human resources are finite (even if Apple's cash reserves are barely so).
That said... What percentage of Apple's user base lives with disabilities? What percentage is visually impaired; what percentage has motor difficulties? These are clearly worthy, comparatively small populations of users that Apple devotes an otherwise-inordinate amount of development resources to. Maybe it's time Apple considers melanopsin sensitivity worthy of admitting to this circle.
- wpietri 11y agoIt seems to me that there could be a half-way model. Some permissions are surely problematic to give to everybody. But perhaps they could then not give them to absolutely everybody? One option would be to require preapproval. The other would be to say that they are sensitive, such that Apple gives apps that use them a much lower threshold for complaints.
- madeofpalk 11y agoPeople don't seem to take to nicely to Apple when they give preferential treatment for developers and allow some to access APIs that others can't.
- cortesoft 11y agoThe other option for Apple was to do nothing - not do any public API development, but also not send a C&D notice to f.lux.
- MBCook 11y agoI'd imagine they don't want to end up looking like they're encouraging this behavior in anyway (including tacitly). Flux may be relatively harmless, but that might not be the case with other apps.