Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
That's fine, but why did you allow it in the first place!? Who reviews these!? Can just any random terrorist put an app on the app store? Wth...
 
Saw this coming from 10 miles away, which is why I didn't buy it. Nobody here has an excuse if they bought it. Apple is notorious for doing this and MacRumors has repeatedly talked about how Apple is coming out with the same feature in a few weeks. If you want it now, install the public beta which is pretty stable. One of my first thoughts was that it would increase battery drain using some sort of trickery and I wanted no part in that. I'm sure he made a nice little sum off of it by being cute with the way he did it to get it onto the store, so he doesn't want to push things any further and still get paid.
 
So:

- Basically using private APIs, even though not directly.
- Claiming your app does one thing so that it can run in the background indefinitely, but it actually does something else.

Yep, no surprise this got pulled.

Yeah, and why was it approved in the first place? The reviewers should know a little bit better than this, ...
 
i have no problem with this. i can only imagine the mess it would cause with the average user dealing with third party apps and the troubleshooting nightmare it would cause, especially on the eve of the feature being implemented in iOS 9.3...

imagine the average user complaining that their pictures look yellow or different and associating it with the camera or their screen and apple not being able to assume in any measure the fault of any one given app
I can't argue this point, still dumb that it slipped through their approval system in the first place though
 
What is a private (non-public) API in iOS context? I thought every app was sandboxed and thus could only use public APIs provided by the SDK. Why can 3rd party developers access these private APIs through the SDK? Why leave it up to human intervention to block their use?
 
  • Like
Reactions: sd70mac
I don't see the point to this app anyway. I prefer a white screen. Have no plans on changing it.

As soon as 9.3 comes out I'm turning Nightshift off.
 
vintage lite brite 3.jpg This is more efficient way...and technological advanced.
 
And this sort of thing is an example of why I went to Android again.

Don't get me wrong, this isn't a hater comment, they're both great. But if you want to hack around with third party system tweaks, iOS ain't the place to be. I figured when the story of this being approved came up it'd have been a mistake.
 
Good. Apple has strict approval policies to maintain a certain quality of apps.

Of which Flexbright was not.

Oh, there are still plenty of low quality apps in the App Store. Plenty. I doubt very seriously that Apple killed this app because of its quality or lack thereof. They likely killed it because its functionality closely resembled a feature that will soon be coming to iOS.
 
And this sort of thing is an example of why I went to Android again.

Don't get me wrong, this isn't a hater comment, they're both great. But if you want to hack around with third party system tweaks, iOS ain't the place to be. I figured when the story of this being approved came up it'd have been a mistake.
And there is NOTHING WRONG with that. People shouldn't be labeled as a hater because of that.
 
As a developer I can go on and own how hilarious Apple's App Store review process is - the level of irritation we have to deal with and yet things like this getting approved just shows what level of education and training the reviewers have and how misguided (mismanaged) it is.
Which pretty much apples and has applied for ages to essentially anything that involves humans.
[doublepost=1457559623][/doublepost]
Oh, there are still plenty of low quality apps in the App Store. Plenty. I doubt very seriously that Apple killed this app because of its quality or lack thereof. They likely killed it because its functionality closely resembled a feature that will soon be coming to iOS.
Or essentially because of the reasons that Apple provided, as mentioned in the article.
 
And this sort of thing is an example of why I went to Android again.

Don't get me wrong, this isn't a hater comment, they're both great. But if you want to hack around with third party system tweaks, iOS ain't the place to be.

This is true, but letting developers "hack around" means that people who don't have good intentions can also do some hacking. I'll take the walled garden that prioritizes security.
 
Apple is so full of itself when it does stuff like this. I hate to say this but I'm really glad that Microsoft is finally giving them a run for their money in the desktop and laptop space. Now with something like the Galaxy S7 from Samsung which has force touch and animated photos. Honestly Apple needs to mellow out a bit and let their app ecosystem flourish.

Are you serious? This app is violating apple policies on two levels.
First it's a hack by using non public API. An app is self contained and shouldn't be able to change system wide setting in iOS architecture.
Second, the hack involves a fake music player to keep ap (application processor of the soc) awake constantly. This is called a power assertion in iOS (like wake lock in android), which is extremely frowned upon. Even android has started clamping down on it (project Volta last year and an even more stringent API this year). In essence your phone battery relies on the operating system to intelligently lower the soc power into sleep mode as much as possible when screen is off (most of the time in a 24 hrs period). By keeping it awake 24 hrs a day the soc will draw power consistently and shorten your standby battery life by as much as 10x. (Standby power is extremely sensitive to power assertion. Also the app has to be awake even when screen is off just so it can continue to run in the background.)
Source: I worked on iOS operating system.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.