we have almost 2 million apps to choose from in Apple's app store. i think they're doing alright.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Pulls 'FlexBright', Says iOS Apps That Adjust Display Temperature Aren't Allowed
- Thread starter MacRumors
- Start date
- Sort by reaction score
I think it's very important for all of us to know that you feel there is nothing of significance here for the rest of us to think about or discuss. And at least you gave us reasons for your conclusion and subsequent proclamation. Very impressive, indeed. What's next?
If he never did actually call into the private API, then he's not using them. It sounded like he recreated the effect of the private API (using a technique similar to the technique used in the code behind the private API.) That's legit in my book. Much of the time, the reason APIs are private is that the names/calling conventions of the function(s) are not guaranteed to remain the same, and you will not receive advance notice of any changes to that effect. There are private APIs that do trivial things, but that doesn't mean that you're not allowed to do those trivial things, just that you can't use that API to accomplish it.
Nah.
It is debatable.
Your assertion has no merit.
There are plenty of tech savvy people who just choose not to buy Android for whatever reason.
Just as there are plenty of Android users who are just not tech savvy.
Those are some interesting stereotypical generalizations.
[doublepost=1457570313][/doublepost]
Not just every single app, but "EVERY SIGNLE APP" has "in-app purchases"? That lends it all SO MUCH credibility.
LOL, I knew there was no way they were doing this without using private APIs. That didn't last long.
Is it still safe to use the app, which is using private API?
I got the app before its pulled. Its working great but it does drain battery a lot.
I got the app before its pulled. Its working great but it does drain battery a lot.
Because it's pointless to write new features for 32bit devices they don't even sell anymore? It costs money and time. Increases the amount of code required to support it for aging, obsolete devices. It's only a matter of 1-2 more iOS generations before its 64bit only, dropping all ancient 32bit code completely.
[doublepost=1457571719][/doublepost]
Why would you use an app that essentially never allows your phone to properly be put to sleep? That's ridiculous.
I wish they'd extend the maintaining of quality to their app store and other services....
https://www.macrumors.com/2014/09/04/app-store-itunes-radio-outage/
https://www.macrumors.com/2015/03/11/app-store-itunes-connect-down-march/
https://www.macrumors.com/2015/03/26/apple-services-experiencing-outage/
https://www.macrumors.com/2015/06/02/icloud-and-itunes-experiencing-widespread-outage/
https://www.macrumors.com/2015/06/02/app-store-apple-tv-downtime/
https://www.macrumors.com/2015/07/21/apple-music-beats-1-itunes-down-vma/
https://forums.macrumors.com/threads/mac-app-store-is-down-confirmed-by-apple-support.1932983/
https://www.macrumors.com/2015/11/12/mac-app-store-apps-damaged-expired-receipts-issue/
https://www.macrumors.com/2015/11/17/apple-services-down-november-2015/
https://www.macrumors.com/2016/02/04/app-store-itunes-downtime-feb-2016/
Exactly.
They limit functionality for a reason. Look at how people went nuts when they found Facebook was eating up battery life. Now imagine the battery life hit that many of the Android add ons eat. Silliness like moving backgrounds can eat more than 50% of the battery by themselves.
It may mean a small bit more limited functionality but the limits Apple puts in place mean a far far better user experience for the masses.
Look up FlexBright in the iOS Settings and disable Background Update (or whatever it's called in your language of choice). The blue filter works anyway and there's no battery drain. Maybe the backgrounding is needed for the eye strain measurements.
My biggest problem with the app is that it doesn't just lower the colour temperature – it also gives everything a strong greenish tint. According to the developer this is fixed in version 2.1, which will unfortunately never be released.
Technically speaking "Background App Refresh" doesn't control the ability of apps to be able to run in the background as that ability is built into iOS and has been around before Background App Refresh has been introduced (and also doesn't have any user-facing controls to be disabled, aside from indirectly by closing an app to stop it from being able to run in the background).
I was unaware of the night shift feature. You can get away with little tweaks. The loss of detail would be noticeable on significant shifts, as you're basically mapping to a smaller subset of the gamut. I'll look up f.lux.
"I recreated three classes based on non-public APIs."
Well, there you go. Seriously, I have no sympathy for whiney "developers" that don't even get this. Why risk it? Unless you want to have a quick grab of cash? I mean come on, using non-public APIs is a big no no.
Good for Apple to weed out these "developers."
[doublepost=1457576494][/doublepost]
As for a paid app, I think those who did should demand refund from the developer.
Well, there you go. Seriously, I have no sympathy for whiney "developers" that don't even get this. Why risk it? Unless you want to have a quick grab of cash? I mean come on, using non-public APIs is a big no no.
Good for Apple to weed out these "developers."
[doublepost=1457576494][/doublepost]
Can't or won't?
As for a paid app, I think those who did should demand refund from the developer.
Except that people on 32 bit devices can't run nightshift, and there are singifcnant numbers of people on 32 bit devices (around 50 percent of installed iPads)
