Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All Apple would need to do is provide an API, which they have likely already written, just not published.

Other developers could use it for f.lux-like applications. For example, astronomy apps would jump on the ability to set a systemwide red tint for preserving light sensitivity.
Yeah, but it would be weird for them to open up just that and not all the other system-wide controls. There's a precedent they don't want to set.
 
How about lowering the minimum brightness too?

my iphone is still too bright in the dark even if the slider is on the far left side
[doublepost=1453027080][/doublepost]
I'd still much prefer an actual dark color theme or night mode. Off-white helps, but having a black background and white text is much, much easier on the eyes in dark environments.

Go to accessibility->accessibility shortcuts (last bottom)->Invert colors

now if you triple click the home button you get inverted colors which is like a dark color theme for reading. Triple click again to go back to normal
 
  • Like
Reactions: Mainyehc
How about lowering the minimum brightness too?

my iphone is still too bright in the dark even if the slider is on the far left side
[doublepost=1453027080][/doublepost]

Go to accessibility->accessibility shortcuts (last bottom)->Invert colors

now if you triple click the home button you get inverted colors which is like a dark color theme for reading. Triple click again to go back to normal
use the accessibility zoom trick to get a darker screen
 
Yeah, but it would be weird for them to open up just that and not all the other system-wide controls. There's a precedent they don't want to set.

Thats no kind of argument. Content blockers and custom keyboards are apps with system-wide influence. You might protest they fail to meet some definition of system-wide but then f.lux wouldn't need to meet that either.

The ability to control screen tint, is trivially easy to secure against malicious use, especially when compared to the two product categories I mention. If Apple were inclined to provide a screen tint API to developers I doubt they would find themselves encumbered by the many odd excuses I've seen in this thread.

Apple have simply chosen not to. Maybe they can't be bothered, maybe it rubs up against their phobia of customisation, but if they wanted to they could enable this before the next beta.
 
  • Like
Reactions: Mainyehc
Thats no kind of argument. Content blockers and custom keyboards are apps with system-wide influence. You might protest they fail to meet some definition of system-wide but then f.lux wouldn't need to meet that either.

The ability to control screen tint, is trivially easy to secure against malicious use, especially when compared to the two product categories I mention. If Apple were inclined to provide a screen tint API to developers I doubt they would find themselves encumbered by the many odd excuses I've seen in this thread.

Apple have simply chosen not to. Maybe they can't be bothered, maybe it rubs up against their phobia of customisation, but if they wanted to they could enable this before the next beta.
Pretty sure content blockers only apply to Safari and Safari controllers and not just systemwide to any app. As for keyboards, those seem to be like a rather specific exception that took some time for Apple to even go with after putting specific controls in relation to them. Even with that it can be argued that a keyboard doesn't really affect another app or what it shows or does in the sense that it appears in the bottom portion of the screen where the standard keyboard appears normally anyway and that doesn't affect how an another app works or looks like or what it does. So it's certainly not just black and white, but there seems to still be more in line with not really having apps that perform system functions and have an affect on the OS itself and other apps vs. the other way.
 
Thats no kind of argument. Content blockers and custom keyboards are apps with system-wide influence. You might protest they fail to meet some definition of system-wide but then f.lux wouldn't need to meet that either.

The ability to control screen tint, is trivially easy to secure against malicious use, especially when compared to the two product categories I mention. If Apple were inclined to provide a screen tint API to developers I doubt they would find themselves encumbered by the many odd excuses I've seen in this thread.

Apple have simply chosen not to. Maybe they can't be bothered, maybe it rubs up against their phobia of customisation, but if they wanted to they could enable this before the next beta.

No they're not. Content Blockers don't work outside of Safari.
 
It's a system-wide thing, and because of that, Apple wants control of it. I don't see what's wrong with that?

You don't see what is wrong? How about stealing someone's invention and claiming as your own and blocking the original inventor from doing business on your platform. What Apple has been doing for years while suing everyone else for doing it with them
 
You don't see what is wrong? How about stealing someone's invention and claiming as your own and blocking the original inventor from doing business on your platform. What Apple has been doing for years while suing everyone else for doing it with them
Where did that happen? What invention are we talking about? Plenty of companies have their own versions of browsers or word processors or calculators--are they all stolen somehow because there are different implementations of something by different companies/people?
 
You don't see what is wrong? How about stealing someone's invention and claiming as your own and blocking the original inventor from doing business on your platform. What Apple has been doing for years while suing everyone else for doing it with them

They're not blocking them because they're competition. They don't like people side loading fully configured programs with no source code. And why would they?
 
You don't see what is wrong? How about stealing someone's invention and claiming as your own and blocking the original inventor from doing business on your platform. What Apple has been doing for years while suing everyone else for doing it with them
Sorry, f.lux didn't invent changing color temperature on displays. Do you have a specific implementation that they patented that Apple is ripping off? If one exists they should sue.

Where did that happen? What invention are we talking about? Plenty of companies have their own versions of browsers or word processors or calculators--are they all stolen somehow because there are different implementations of something by different companies/people?

Any developer creating an app that's basically a system wide function should know that eventually Apple will bake it into the OS, especially if it's popular.
 
This is a great, great app on my iMac. Would love to see this on my iOS devices. Just realized last night on the iMac that you can be working with iPhoto, or other apps, have it in night mode and it will remember to override that mode for specific apps. How great it that!!! Will Apple's solution do that? If your working at night and flipping between apps, and one is iPhoto this is a great feature. Or Apple, just buy them out, and give us the full Flux experience on iOS:)
 
This is a great, great app on my iMac. Would love to see this on my iOS devices. Just realized last night on the iMac that you can be working with iPhoto, or other apps, have it in night mode and it will remember to override that mode for specific apps. How great it that!!! Will Apple's solution do that? If your working at night and flipping between apps, and one is iPhoto this is a great feature. Or Apple, just buy them out, and give us the full Flux experience on iOS:)


I don't know if it will, but I can tell that for now it doesn't. It's system wide and the only variables you get are schedule on/off and modified colour temperature. But it's better than nothing, even the f.lux app for iOS isn't as good as the desktop counterparts - It doesn't have 3 time periods for a more gradual effect nor does it have the per-app overrides you're inquiring about.

Hopefully Apple can weasel in some of the desktop features if they're not going pay for them.
 
They should be sued for implementing the "Night Shift Mode" which is a clear blatant rip off of F.Lux. Honestly this is such BS and of course all the ignorant MacRumors posters are like "BWAH HAHA APPLE STOLE IT LOL SUX TO BE U" and ignorant people on Facebook are going to be like "OMG It's so INNOVATIVE".

This comment is hilarious! Thank you! Everyone that had a flashlight app or a calculator app should sue Apple as well eh?
 
Agreed. Now Apple has come up with the perfect solution, nobody needs F.lux on their iOS devices to clone a core OS feature.
Hardly a perfect solution. Previously, it was a third party app that users could choose to install. Now it's undeleteable junkware like half the rest of the unwanted apps that come pre-installed.
 
Hardly a perfect solution. Previously, it was a third party app that users could choose to install. Now it's undeleteable junkware like half the rest of the unwanted apps that come pre-installed.

It's just another setting in the Settings app. Granted, the settings app has gotten very crowded, so adding another item might not be optimal, but it's hardly "undeleteable junkware."
 
If you have bashed Samsung for copying the iPhone and now give Apple a pass on this... you just might be a sociopath.
 
Well, iOS 9 looked cool, but now I'm seriously regretting installing it as it has noticeably slowed down my iPhone 6. WTF, Apple?! Fix your ****!
[doublepost=1453154457][/doublepost]
Thats no kind of argument. Content blockers and custom keyboards are apps with system-wide influence. You might protest they fail to meet some definition of system-wide but then f.lux wouldn't need to meet that either.

The ability to control screen tint, is trivially easy to secure against malicious use, especially when compared to the two product categories I mention. If Apple were inclined to provide a screen tint API to developers I doubt they would find themselves encumbered by the many odd excuses I've seen in this thread.

Apple have simply chosen not to. Maybe they can't be bothered, maybe it rubs up against their phobia of customisation, but if they wanted to they could enable this before the next beta.
Nothing they've allowed is as system-wide as controlling the entire screen tint all the time. These apps could conflict with each other and with system features like auto-brightness and Apple's own f.lux copy. It's much more natural to add a keyboard, just one more option in the keyboard list that used to only include Apple's keyboards.

BTW, my iOS devices have almost always been jailbroken. I've been able to play with endless customization, and it never helped much more than what Apple provided (except back in iOS 3). I can totally see why Apple doesn't want to allow stuff like that.
[doublepost=1453154710][/doublepost]
How about lowering the minimum brightness too?

my iphone is still too bright in the dark even if the slider is on the far left side
Yeah, same.
 
Last edited:
There is nothing slimy about this. Apple doesn't now, and has never on the past, allowed ANY developer to add an OS level feature to iOS. Build apps all day long, but the OS is out of the question. I don't know why this is so hard to comprehend. People that want to add 'features' have to go around Apple via side loading or jailbreaking. Neither of which is a good idea for the majority.
I'm not sure you understand how frustrating it is to have a product that you know people want and to be prevented from even offering it because of some bureaucratic ********. I can't think of anything that bothers me more as a developer than having these artificial barriers placed in the way. I don't blame Apple for implementing the idea themselves, but I do blame them for denying f.lux access to the platform at the same time.
 
I'm not sure you understand how frustrating it is to have a product that you know people want and to be prevented from even offering it because of some bureaucratic ********. I can't think of anything that bothers me more as a developer than having these artificial barriers placed in the way. I don't blame Apple for implementing the idea themselves, but I do blame them for denying f.lux access to the platform at the same time.
But it's not some bureaucratic stuff or something like that, it's basically something that relates to the foundation of how iOS has been designed from the beginning. I can certainly understand not liking that or disagreeing with that, but that's the design principle of the OS that has been like that from its initial stages essentially, not something just made up just because basically or something new or anything like that.
 
How about lowering the minimum brightness too?

my iphone is still too bright in the dark even if the slider is on the far left side
[doublepost=1453027080][/doublepost]

Go to accessibility->accessibility shortcuts (last bottom)->Invert colors

now if you triple click the home button you get inverted colors which is like a dark color theme for reading. Triple click again to go back to normal

Thanks, been doing that for years. It works well enough in certain apps but since there are dark screens or parts of screens, I still get blinded.
 
Apple looks like a bunch of dicks not allowing this in the app store.

I don't see why. Any JB dev should know that at any point iOS might integrate what they're doing. BiteSMS already went through it, I'm sure that other tweaks have had it happen as well that I'm not aware of. If devs don't want their stuff to be integrated into the OS itself then they should probably go through the app store or work on something else.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.