interesting - I am more worry someone with a calculator app adding 120MHZ just because
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 Says Third-Party Apps Can Take Full Advantage of ProMotion With Plist Entry, Core Animation Bug Fix Coming [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
I'm more worried Apple thinks they know better than the owner of the device and limits Safari to 60Hz or less when it's one of the commonly used apps to benefit from 120Hz.
It's pretty clear to me that they made another oppsie and didn't want to admit so they just made up a new requirement. How can you release a new product with software that doesn't work well with your own products (AirPods Pro and Apple Watch) and doesn't even utilize the headlining feature to its full potential? There are already a bunch of features missing. What were they doing all this time?! The only other explanation (and I really hope it's not it) is that they wanted better battery scores so they left it out on purpose.
This is pretty ill-informed. The rather extensive documentation on this feature shows they didn’t just make it up last night. The way it works is well-reasoned and very-well explained in the developer documentation. And the support is already in the operating system - it just requires developers to opt in by editing their plist file (which is not source code). The software works fine will AirPods Pro and Apple Watch, it uses the headlining feature to its full potential (promotion is NOT “120Hz at all times” but “variable speed to increase battery life to double the old phones“), its own software already runs at 120Hz when appropriate, and it will have no affect whatsoever on the battery scores.
And that “oppsie” is what, exactly? They forgot that apps might want to use this?
No, you’re wrong. Tim Apple engineered an evil plan where we’re forced BY LAW to buy new iPhones on day one, only to realize some apps don’t actually support one of the new features yet. But he didn’t count on a lone developer on Twitter who found out all about it! Drat!
What do you mean by this? I played with a 13 Pro in store last night and compared scrolling in Safari side by side with my 12 Pro Max… Safari was definitely running in 120 Hz because the difference was obvious.
It refreshes at 120hz when it determines that doing so would be of benefit - depends on what is being rendered, how fast you’re scrolling, etc. Seems like a fine compromise to me.
That last part is the part that confuses me the most. If Apple knew and always planned on it being a KVP setting, why wasn't that communicated during the developer beta process? Knowing it and holding back would be poor behavior, and so would knowing it but assuming that communication had been made without ensuring it had. Either of those speaks poorly about Apple's developer communication process, which frankly has already been pretty bad for several years.
There was no beta process for this feature. It was announced with the iPhones 13. iOS 15 betas didn’t have it.
This hasn’t been communicated flawlessly, but it’s also making a mountain out of a molehill.
The iphone 13 was announced 2 weeks ago. xcode was updated a week ago. It’s not like apple’s been hiding this issuse for months - until a couple of weeks ago there were no products even announced which had this feature.
Why worry? If a calculator app is able to do 120fps, it will spend almost all it’s time at 10fps as the feature is adaptive to what’s going on.Which is what that guy already did
Apple has had an internal build of iOS 15 with this feature for a while. They chose to remove the feature from builds distributed publicly. They absolutely hid it so they could “surprise” people at the keynote.
Based on previous posts regarding dealing with issues in Apple products including by some of the same posters here:
1. Developers and end users should send feedback to Apple for issues.
2. Developers and end users should trust Apple to always resolve issues without having to be told about them.
3. If there is an unresolved issue with Apple products, developers or end users will be blamed for not reporting the issue.
4. Anyone who suggests that during Apple's iPhone 13 Pro announcement, Apple could have had the speaker say a single sentence like "Developers will be able to take full advantage of ProMotion in an upcoming iOS update" as well as include the same sentence on the iPhone 13 webpage, will be met with backlash for suggesting that Apple explain themselves to mere lowly developers.
1. Developers and end users should send feedback to Apple for issues.
2. Developers and end users should trust Apple to always resolve issues without having to be told about them.
3. If there is an unresolved issue with Apple products, developers or end users will be blamed for not reporting the issue.
4. Anyone who suggests that during Apple's iPhone 13 Pro announcement, Apple could have had the speaker say a single sentence like "Developers will be able to take full advantage of ProMotion in an upcoming iOS update" as well as include the same sentence on the iPhone 13 webpage, will be met with backlash for suggesting that Apple explain themselves to mere lowly developers.
Yes, and?
I think they should’ve done something of the sort, yes.
What an awful example, that's EXACTLY what happens - they release features like Rebar, DLSS and RTX and then companies have to update software to support those features. It's far far worse (and far less supported) than any new tech released on the iPhone. We're still waiting for Rebar support a year after the 3000 series on more than a handful of games.
No one is denying *that*. The point is that it was publicly announced, within a couple of weeks the developers have all the information they need, and within a couple more there will be lots of apps that support it. So what’s the problem exactly? There are *already* apps in the app store that support it. 24 hours after the phone was released.
It’s *never* been the case that all apps support every new feature on the day an iphone is released.
I was correcting the poster I responded to. No “and” necessary. I don’t really have an opinion about what the right thing to do was, but the only reason this issue is being discussed is because Apple felt they needed to hide this feature from developers until the official announcement of the 13 Pro. Had they included documentation before the event, developers wouldn’t have been caught off guard and scrambling to figure out how to enable 120 Hz for their app animations.
I agree, it’s not a big deal and I’m not sure why people are making such a big deal about it. I mean, yes, Apple could have had better developer documentation ready on the day of the announcement so that devs wouldn’t have been confused and scrambling for answers when they received their phones, but in the end, it’s a very minor thing that seems to have been resolved quickly.
It's A LOT better than it was - when we went from iPhone 4S to iPhone 5 it took Instagram about 3 months to update for the new screen size
Poor comparison. And seriously, this is a first-world problem. It's not a "degradation" of performance on devices.
A GPU dedicated to do one thing is very different than a full hardware device + operating system + support system. We need to give Apple _some_ allowance for certain oversights. While iOS was offered for public beta testing, hardware devices are not, so was there even an opportunity for public testers to have caught this? I'm guessing not. It was caught *the same day* as the device launches, and addressed. I fail to see where the complaints are justified.
I'm not sure that's a fair comparison. Dark Mode quite often requires app developers to build a complete second set of visual assets that work "in reverse (white on black)", and not just some developer coding needed.
And I fear the opposite. Developers that don't need ProMotion will enable it and waste device resources for absolutely no benefit to the user. This is why I'm also against giving developers unlimited RAM... because they will abuse that endlessly. I applaud Apple for having a very conservative approach to system resources, forcing developers to optimize.