Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
but can you give me one precedent where a third-party app is allowed to change system settings on iOS?

First, what is a system setting? Is something a system setting only because Apple puts it in the "Settings" app? If so, it's kind of odd that Personal Hotspot is in the settings because that is a bonafide functionality that could be a standalone app. Likewise, the Watch app is really mostly settings, so it is odd that it isn't in the Settings app. I don't question Apple's choices here, I question your emphasis on the distinction. I think it's a distinction without a difference.

To answer your question though, many apps play sounds even if the ringer switch is on vibrate. Apps can change the brightness of the screen - surely that is a "setting" and incidentally a very close comparison to changing the hue.

And there is a big difference between read and write access (location, photos, address book are largely read access only, eg, while you can add photos you cannot delete photos via third-party apps). Getting read access to data is quite different than altering the (screen) output of other apps.

Isn't the ability to add and create photos by definition write access? It's certainly not "read only." Likewise, Apple is clearly giving users manual control over certain screen variables that control hue. Just like Apple offers developers an API string for changing brightness, they can just as well offer apps an API string for changing hue. Just like they let music continue in the background, they can just as well let this change be persistent. Just like they let uploading apps continue to run for weeks or months at a time (e.g., I haven't opened my Flickr app in months, yet it still uploads new photos I take automatically), this can too.

None of this is new.
 
Apple's done this before, so there's a precedent and they'll not allow f.lux back in, as they now have that feature and don't want another app competing.
 
Apple's done this before, so there's a precedent and they'll not allow f.lux back in, as they now have that feature and don't want another app competing.
Well, to be fair, all kinds of flashlight apps have been there and are still there despite Apple natively offering that feature for a number of years now.
 
  • Like
Reactions: Benjamin Frost
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.

Ignorance isn't an excuse. You are supposed to exercise due diligence when offering a product for sale, and that includes researching to check if it possibly infringes existing patents. You are confusing this with copyright, where yes, you can claim ignorance as a defense if you haven't seen the work you are accused of infringing.
 
How does F.Lux make money off of the free Mac OS version of their software? It seems like a great idea. I want this for my phone, but I'm skeptical about downloading software that takes over my machines which is free.

If it is voluntary pay, I will send them some money and feel like I get them and that they aren't looking for some other revenue stream.
 
First thing: Is this true about the blue light? Does it really help to use F.Lux?

I don't think it matters if it's "true" (in terms of circadian rhythm) because it's still subjectively less harsh to a lot of people to see a "warm" screen at night rather than the "cool" screen during the daytime. Primally, you can think of it as being closer to the light given off by a fire at night vs. the light given off by the sun in mid day :)
 
  • Like
Reactions: Benjamin Frost
I like this response. They could have gone all "Apple is stealing our lunch money and we demand yada yada yada." But they didn't. The response was well thought through and diplomatic, making a request and bolstering their position without being seen to attack or deride. Well done whoever drafted that thing.
 
That's just not true. Even my wife, maybe the least tech savvy person on the earth, ask me what to allow and what not to allow on her iPhone.
And people just pressing allow without second guessing, well, they deserve security breaches...

And thus, the class action lawsuit was formed.

Good to see your wife is informed though, she is better than most (not referring to only women).
 
I'm pretty sure Sherlock was an Apple feature that ultimately gave way to Spotlight. Was there a third-party predecessor that Apple stole the idea and the name from?

Ha yes sorry, I got the names mixed up, can you believe it or not it was called Watson! It was by Karelia Software.
 
It's too bad that Apple has to COPY a competitive app, ban competition for at least a few months after the OS update to promote their own feature, release a naive and buggy version of what the competition offers, and then have to fix the app numerous times until it matches the original innovator on features.

Apple is so quick to go after people that steal their IP (like rounded rectangles) that is just sad when Apple blatantly is anti-competitive and rips off smaller company's IP. I mean, come on Apple, at least buy out f.lux to avoid total hypocrisy.

Microsoft got slammed in the 90's for building into Windows features that competitors were trying to offer; it's just a double standard and insane that Apple is allowed to do the same thing, but on top of that has full control of a DRM protected app marketplace and can ban competitive apps from being installed, which is totally worse than Microsoft ever accomplished for anti-competitive behavior.
 
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!!

Have you tried the app-specific auto-disabling or the 2-hour movie mode? They work fine for colour-critical work and watching video content, IMHO…

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.

As another user mentioned, it is a scheduled and gradual process (which Apple didn't, AFAIK – because I'm not running the beta – bother to emulate? Guess I'll just keep running my sideloaded copy of F.lux until it craps out on me, then…), and it offers, apparently, a lower lowest colour temperature setting (yet another reason to stick with F.lux).

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.

F.lux already offers a Darkroom setting which could be a killer feature for photography development, especially if run on a future iPhone with an OLED screen, and which would work great for the applications you just mentioned.
 
How does F.Lux make money off of the free Mac OS version of their software? It seems like a great idea. I want this for my phone, but I'm skeptical about downloading software that takes over my machines which is free.

If it is voluntary pay, I will send them some money and feel like I get them and that they aren't looking for some other revenue stream.

no idea but flux works great.
 
1, it doesn't - see flux.

2, you're supposed to upgrade to new hardware.

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.
'
 
  • Like
Reactions: alvindarkness
Geekbench provides nothing.
Except a rough understanding of how much slower one computer is versus the other. For your iPad mini that's a fifth of the single-core speed of an iPad mini 2, which will get Night Shift.
How many cpu cycles do you think it takes change screen temp?
How many CPU cycles do you think should be left free for the active app, after the system has done it's thing? Maybe Apple thinks the iPad mini's A5 chip is already underpowered to run Safari (without Night Shift, Content Blocker or Split View) in the snappiness they want to achieve. Maybe the few iDevices with an A6 chip are not worth the effort to rewrite libraries in 32-bit. Maybe going 64-bit-only makes development easier in the future. Maybe it's a combination of reasons.
I think only developing for 64bit OS's explanation is far more reasonable, although not entirely explanatory as to why developing it for 32bit versions of iOS would've been that taxing on Apples large resources.
Programming something twice is always a large taxation, because it is unnecessary work. Reusable code is what makes programmers efficient. 32-bit code has no use in the future. And Apple wouldn't get applause for doing the effort. People would take the new feature for granted and complain about planned obsolescence anyway, because their old devices would run just a tiny bit slower.
Again, F.lux works perfectly well on old devices.
But it could cause problems with every single update. The point is, Apple can't control it's perfect behavior and therefore won't allow it to run constantly in the background and change the look and feel of every foreground app. This kind of access is not provided to any third party developer on iOS, not on old and not on new devices, not in the past and not in the future. This is a platform-specific constraint, live with it or leave iOS for good.
I would have continued to use F.lux either way, as I would've continued to jailbreak either way.
And in doing so, you are leaving Apples way and are yourself responsible for how smooth the system is running. Jailbreakers have activated all kinds of features on older devices, claiming they're running fine. Siri on iPhone 4 and what not else. I've decided against jailbreaking like most people.
I commented on their lack of support for "older" devices like the iPhone 5 (which is still a very capable phone), as it to me it sends an obvious message from Apple to its customers.
And the message is that Apple is doing the 64-bit transition sooner and quicker than anyone expected. Not only to make iDevices from as early as 2013 faster, but to create a bigger chance for using the same code under iOS and OS X. The whole Metal framework exists in 64-bit land and it aims at graphic-intense cross-platform mobile-and-desktop applications. This is the real deal, not if some new convenience feature is available on a certain older device. The ability to use Night Shift on an iPhone 5 is unimportant to the future of the iPhone platform.
Some people think that its perfectly acceptable to upgrade your phone every year, or biyearly. Apple has instilled a sense of it as being normal.
It's been the european telcos who invented 2-year contracts with subsidized cellphones long before smartphones even existed.
As a consumer, I will decide where and how I spend my money. A lot of my decisions are made based on previous experiences, and how I perceive the moral behaviour of a company to be.
And your judgement isn't universal for everybody.
It is why I don't use any google services, and don't use a microsoft OS.
Rubbish, most of their products and services are just bad even if you buy their newest device. That's the main reason why they are avoided. Some people maintain older Windows and Office versions, because they provide a better experience for them than their newest iterations. On Apples part, you do want an iPad mini 4 with Night Shift, you just don't want to pay for it again. If you win the lottery and money suddenly is no longer a problem, your view on Apple will change dramatically. Whereas you will keep avoiding Googles free services and Microsofts broken OS.
Radeongate has left me feeling that Apple are a bunch of arseholes that couldn't care less about its customers - deciding to only repair their flawed laptop after a class action law suit was building steam. Apple, to me, is slowly slipping into a similar hole as the others, and I am slowly moving toward linux.
You want to switch OS's, because of a hardware defect in a graphic chip (which Apple offered to repair anyway) ? Makes (no) sense to me.
Nothing to do with entitlement. It has to do with observation and making decisions based on those obsevations - irrespective of how they may be perceived by others.
Do what you want, but don't keep us informed. This is not the Ubuntu on Phones forum. We already decided for iOS and want to read rumors about it's future. We know it's traits or shortcomings if you like and have chosen it anyway. Night Shift only continues a trend in which Apple enables features previously available on more open systems (like third party keyboards, browser add-ons etc.) without giving up tight control about what's happening in iOS. That's why no matter how buggy the app, a single push on the home button always sends the phone back in a stable state, ready to make a call. This is the experience Apple wants to provide, not what you want to see fit.
 
Last edited:
Well, to be fair, all kinds of flashlight apps have been there and are still there despite Apple natively offering that feature for a number of years now.
I wasn't referencing flashlight apps. Back in the day there was an app called Konfabulator, which allowed widgets to be on the screen. It was a nice little app, and Apple stole it and basically killed off the developers means of making money.
 
  • Like
Reactions: Benjamin Frost
Well, since it's now mimicking an iOS feature, the chance to get into the app store is probably smaller than ever.
 
I wasn't referencing flashlight apps. Back in the day there was an app called Konfabulator, which allowed widgets to be on the screen. It was a nice little app, and Apple stole it and basically killed off the developers means of making money.
I understand that, I was just pointing out that while things like that happen there is also the other side of it where apps that provide the same kind of functionality that gets built in continue to exist without an issue.
 
It's too bad that Apple has to COPY a competitive app, ban competition for at least a few months after the OS update to promote their own feature, release a naive and buggy version of what the competition offers, and then have to fix the app numerous times until it matches the original innovator on features.

This is why the public is a terrible place to get information. The application is using a private API, which is an automatic reason for rejection from the app store.

While it feels good to get all self-righteous about competition etc, the reason it was banned was because of the API usage, not because Apple was copying it.

That's what happens when you sell a feature instead of an application: eventually the platform vendor will absorb the feature if it's any good.

If you don't like the way it works, form your own company and do it your way.
 
  • Like
Reactions: Rogifan
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.
wrong, wrong, wrong. only apps you give permission to can do those things, and even then they can only do it within their own app -- they cant listen or watch at any time from anywhere, the way this app would need to. thus the use of private APIs, which is a known no-no.
 
  • Like
Reactions: thermodynamic
I understand that, I was just pointing out that while things like that happen there is also the other side of it where apps that provide the same kind of functionality that gets built in continue to exist without an issue.
Except in this case, f.lux for iOS never existed (outside the jailbreak community) in the App Store. They can't even claim to be ousted by Apple, because Apple never let them in in the first place. As long as Night Shift isn't announced for OS X, Apple is not even in competition with f.lux. All there is, are demands to break the App Store rules, because the f.lux duo claims to have good intentions regarding chronobiology.
 
Last edited:
It's a system-wide thing, and because of that, Apple wants control of it. I don't see what's wrong with that?

I agree. An OS is relevant to systemwide tasks pertinent to the device it's running on. While OS companies don't foresee and implement everything, Apple does lock down its OS in the name of security - and while nothing is bulletproof, Apple's job on security is good and that is a reason why. To keep entry points minimal.

With luck, Apple will buy the source code and tweak it to meet their security standards. That'd be cool.
 
Name one app that controls system wide preferences....none. Why should flux be any different? That's not how iOS works. iOS controls system prefs. The fact that the private API even existed shows that Apple was prepping for Nightshift for some time. I use F.Lux on the Mac. It's nice. But they need to pivot to something new, stop whining.
 
Ignorance isn't an excuse. You are supposed to exercise due diligence when offering a product for sale, and that includes researching to check if it possibly infringes existing patents. You are confusing this with copyright, where yes, you can claim ignorance as a defense if you haven't seen the work you are accused of infringing.

Actually, patent law allows for treble damages if you willfully infringe. That's the reason why large companies tell their employees not to look.

1) I'd rather settle, and barring that, not suffer treble damages if we fail to settle.
2) I'd rather not open myself up for treble damages because someone was curious about a patent in an unrelated part of the company (say, Apple getting hit with treble damages because someone in Pages looked up a cellular radio patent at one point that was found in discovery).

The system of additional damages in the case of willful infringement makes it desirable to just do whatever makes sense in isolation, and pay royalties when needed through settlements, rather than risk treble damages because you screwed up a patent search or the court disagrees that you don't infringe because of some detail that you thought made it different.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.