Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Reading this with f.lux active on my Mac right now. This is a dick move by Apple, but I can see the day when they open up the APIs necessary to allow third party alternatives (like f.lux, the inventors of this technology). It is exactly analogous to third party keyboard support, which Apple eventually relented on, to their credit.
[doublepost=1452836162][/doublepost]
Only Apple will ever develop system-wide features. That was a given day 1. Don't like it then go somewhere else.

Third party keyboards says you are wrong.
 
I was about to install f.lux on my MacBook Pro, but now I'll wait a little bit: I'm sure after iOS it will be developed for OS X
[doublepost=1452837159][/doublepost]
Apple looks like a bunch of dicks not allowing this in the app store.
Apple want to maintain control of iOS behavior,miso no point in letting third parties apps mess with it, especially if they are planning to do that by themselves.

does f.lux have a technical requirement of 64bit processor? If not then why does apple have it?

I have an old, original iPad mini that I use just for Netflix and twitch stuff to fall asleep - f.lux or night shift would be great on this old device.
There are people constantly whining about stuttering and lags (mostly non existent) on iOS. I'm glad Apple don't want to put another background process on such an old hardware.

All apps can listen in on your microphone, or track your location or scan your contacts or peek through the camera. But turning your screen a bit yellow? No, we can't think of any way to stop that being a massive security breach.
iOS ask you permission to let some apps to have access to those functions.
As always, the most prominent security breach is ..... the user.
 
If Apple did that, they'd be allowing f.lux to break the rules that all the other developers have to abide by. Everyone else would come complaining to them.
 
If Apple did that, they'd be allowing f.lux to break the rules that all the other developers have to abide by. Everyone else would come complaining to them.

And resources would have to be spent to build APIs that properly adhere to modifying the system for potentially cool things, but would result in even more work just to ensure people don't abuse it - we've seen how that's gone for some vendors with free reign. The benefit to allowing extension of the iOS system is not worth it, yet. They have better things to invest their time into.

In this case, I agree that nesting a feature into the system in Apple's way is superior to the average end user. Sorry but suck-to-suck - people weren't emotional about the Apple Pencil's eventual inertia into Apple's other lines and the death of those third party vendors because it has system level access... And hardware built to cater to it.
 
Problem there is that it would make your shows look all kinds of unnatural and crummy. It's fine when the background of the forum you're browsing turns yellow at night instead of white but it looks horrid when it happens to people and motion graphics. Even watching YouTube with f.lux on is a poor experience.

Precisely. I had f-lux on my Mac and could not have it for more then 2 days. Its OK for reading but for anything else? I prefer to see the colors as true as they can possibly be! Now using this on the TVOS would make everything look like 300 movie! Good thing is, there would be an option to turn it off. I am trying this on the iOS public beta. It's OK I guess but really failing to see why everyone is going banana about it!!
 
Hahaha, hilarious, after Apple announced their built-in feature these guys decide to plead with them, I'm afraid it's too little too late for this, no one in their right mind would use this buggy app rather than Apples implementation!
 
Apple has just about the best legal team of any company out there. Do you seriously believe that they didn't bother looking into the current patent application that f.lux has filed?

The norm for most tech companies (including Apple, I think) is to explicitly avoid looking at those sorts of patents so that you can claim ignorance if it ever comes up in court. So yeah, I doubt they did.


And even if they did get a patent granted and Apple was infringing on it, the payout wouldn't be much. How much is their monetary loss, based on the fact that they don't charge for the product? Apple would make a payout and move on.

By controlling the product, f.lux can potentially turn it off or start charging money for it or start making money through ads or whatever at any point in the future. So the damages need not be related to the cost of the f.lux product. In fact, a damage award would be more likely to be based on the amount of money that f.lux would charge a third party for the use of their patents in somebody else's product, which is entirely unrelated to the cost of the actual product from f.lux.


There is a very simple rule for apps on iOS, whatever you do in one app should never affect anything outside this app. It is a fundamental principle that allowed everybody to install stuff at will without any fear of borking things up, of doing any damage. F.lux clearly breaks that rule.

There are very few calculated exceptions from this rule:
...

There are a boatload of exceptions to that rule, starting with app extensions, which allow third-party keyboards to draw custom user interfaces on top of arbitrary apps and handle keyboard input for those apps....

Compared with that, allowing an app to change the display's color temperature is so far down the "not a legitimate security concern" ladder that it fell off the bottom rung and into the lake.

Besides, you don't have to grant blanket permission to use those SPIs. Just grant permission on a case-by-case basis for developers that have a legitimate reason to use them.


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.

Of course they have. They've allowed custom VPNs, custom keyboards, apps that manage Wi-Fi captive portals, configuration profiles that add new root certs....



This isn't something exclusive to Apple. It's something EVERY SINGLE COMPANY in every single industry does, no matter the size. Small companies take features from bigger ones and implement it in their products. Google takes things from others. Everyone takes stuff from everyone.

But not everyone steals ideas from their competitors and then threatens legal action to stop those competitors from continuing to distribute the original product from which they stole the ideas.... Just saying.
 
They should be heralded since the code they use will be 100% their own and implemented, tested and supported. A third party product used from a jail broken device lost its voice the moment they jail broke the device.

They either aren't good and networking and wanted to sell the idea to Apple or truly are too dense for words to think a system-wide functionality would be allowed because they think its cool.

Only Apple will ever develop system-wide features. That was a given day 1. Don't like it then go somewhere else.

You won't because no other platform will make you money like iOS. Stop complaining and create something intelligent and interesting at the user space for people to buy.

Can't do that? Too bad.

One day some company will tell Apple exact same words, because in the world of dense Apple is king.
 
  • Like
Reactions: alvindarkness
I would have been a lot more sympathetic to their cause if they were at least an open-source or community-driven project to accompany their virtuous attitude. For instance, I have been asking them for years to accept translations to make the application more accessible and they always brush it off with ‘it’s planned, stay tuned’. The truth of the matter is that the development of this program is not really moving forward and they seem to be very protective of it all as well. Just check out the EULA they provide, it is very restrictive. When they published the iOS Xcode project for people to side-load, they even went as far as tricking Xcode into placing a precompiled binary into the application bundle, purely so that they don't have to expose any of their algorithms. This is through and through a commercial product and a business for them. The rules of the game are simple: in a free market, everything is up for grabs. If you want to protect your ‘intellectual property’ in software, you better have patent ready.
 
  • Like
Reactions: Narcaz
Does f.lux actually do anything beyond what is observable?
All I noticed was it turning my screen yellow.
I can do that myself with a custom colour profile for my display.
 
Does f.lux actually do anything beyond what is observable?
All I noticed was it turning my screen yellow.
I can do that myself with a custom colour profile for my display.
They do set a special color profile, but it's a dynamic one. It automatically changes so that it matches the sunlight cycle in your region and it's customisable for your sleep pattern.

IMHO it's overrated, but it's still more than just an usual custom color profile.
 
They do set a special color profile, but it's a dynamic one. It automatically changes so that it matches the sunlight cycle in your region and it's customisable for your sleep pattern.

IMHO it's overrated, but it's still more than just an usual custom color profile.

But it is still observable behaviour. All F.lux does is use publicly available information on sun exposure in a given location at a given time and adjust the profile accordingly. It was easy for Apple to implement this, because they use these algorithms in other areas of the system already. All they needed to add is a coupling to the screen colour temperature and a settings panel. That is pretty much it.
 
I rather this feature be directly integrated within the OS over a separate
1ce8.jpg
ht11.jpg
 
But it is still observable behaviour. All F.lux does is use publicly available information on sun exposure in a given location at a given time and adjust the profile accordingly. It was easy for Apple to implement this, because they use these algorithms in other areas of the system already. All they needed to add is a coupling to the screen colour temperature and a settings panel. That is pretty much it.

That is besides the point. The point is this feature just magically appeared in 9.3.
 
  • Like
Reactions: alvindarkness
This is what IP laws were intended to discourage. They don't work, clearly. I hope f.lux embeds a link in their about screen to sites describing all of these shenanigans.
Care to explain?

Except those devices Apple have excluded from having the feature thanks to planned obsolesence. Here are some devices that wont have Night Shift -:
  • iPad 2
  • iPad 3
  • iPad 4
  • iPad mini
  • iPod Touch 5G
  • iPhone 5
  • iPhone 5c

Not to mention their implementation isnt complete. I'll continue to jailbreak and install F.lux.
They did the right thing. Otherwise whiners would have stormed the forum about performance on their old devices like a bunch of them that opened a class action about performance degradation on a five years old iPhone 4S.... (Utterly ridiculous).

Everybody complains how slow older devices are on the latest OS. And that is while Apple is already cutting some features that are performance hogs from the OS these older devices get. So what is planned obsolescence: Offering features (including general OS versions) that slow devices down or cutting features (that would otherwise slow devices down). It seems, whatever Apple does on this front they get blamed.
Absolutely agree.
 
Because suddenly it's magical. Oh and also, because Apple stopped people from installing this app using Xcode.

I see there is no point in debating this with you, but just for good measure: Apple likely intervened on Github, because F.lux modified the public Xcode project in such a way that it would swap in a precompiled binary before the app would be loaded onto the device. That is a can of worms they rightfully do not want to see being opened. If Apple were really against it, they would have taken action against similar open-source projects that provide exactly the same function in their source code, but without the hackiness, like: anthonya1999/GoodNight and thomasfinch/GammaThingy as on-point examples.
 
  • Like
Reactions: Narcaz
I see there is no point in debating this with you, but just for good measure: Apple likely intervened on Github, because F.lux modified the public Xcode project in such a way that it would swap in a precompiled binary before the app would be loaded onto the device. That is a can of worms they rightfully do not want to see being opened. If Apple were really against it, they would have taken action against similar open-source projects that provide exactly the same function in their source code, but without the hackiness, like: anthonya1999/GoodNight and thomasfinch/GammaThingy as on-point examples.

Just because Apple included this magical feature themselves. I see why many companies and developers see no point in debating about anything with Apple since Apple has reached such a glorious level of hubris that it is utterly pointless.
 
I can't say I'm surprised. If something works in the AppStore, it gets copied. Flappy Bird clones, etc. Ditto with the software world. The whole mess about Android copying iOS surfaced, but Google got away with that. We're actually better for it now since Android is pretty neat in its own right. If nothing else, it's keeping iOS from getting complacent and stale.
 
There is a difference between read access and write access (and every read access has to be approved by the user for every single app individually). Third-party apps can read the camera roll and add to it, but they cannot delete from it. If an app that changes the colour of the screen misbehaves, it could make the whole phone unusable in an extreme case. Getting access to information is one thing, modifying information is completely different thing.

And referring back to the post you are replying to, you can't think of any way to stop this being a problem? Not even if you give it two minutes of really intense thought?

iOS ask you permission to let some apps to have access to those functions.

Yes it does.
[doublepost=1452849059][/doublepost]
If Apple did that, they'd be allowing f.lux to break the rules that all the other developers have to abide by. Everyone else would come complaining to them.

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.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.