Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Dark Mode is not an easy on/off switch though. A TON of design retooling has to happen for dark mode to be usable.
Yes and no.

Yes, because technically, you can just about flip a switch and have your app "support" dark mode.

No, because if you care about the quality of your product, you will:
1. check every page in your app to make sure it looks good in light and dark mode
2. provide specific colors to UI elements that look good together and look appropriate for light and dark mode
3. create (or have someone create) a new set of image assets so your app looks good in dark mode.
 
Glad to see Apple being proactive on this but you would think this is something they could and should have relayed to Developers once they started accepting iOS 15 apps last week.
Proactive? They have not even prepared the documentation, and it's still buggy. Seems like it's half baked, the hardware is ready but the software barely made it to production.
 
I knew it was a bug.

Like I said. When Apple comes up with a name for a technology, "Retina", "TouchID", "TrueTone", "ProMotion", it means it works the same way on all devices. It wouldn't make sense for "ProMotion" to work differently on the iPad Pro than on the iPhone.
You’re a bug, I’m a bug we’re all bugs. I don’t know I’m bored 🙃
 
Good to see. This is something that should've been communicated to developers before the iPhones came out, not after, so that apps could be updated before the phones came out (like every other iPhone launch).

Let's hope they push updates fast.
 
I remember when iPhone X launched some Apple own apps couldn't even take advantage of the new screen ratio. This thing happens.
That's different. After the X was announced and before it was launched, developers still had all the tools and resources they needed to make their apps compatible available to their disposal. Some people at Apple internally dropped the ball, but developers still had the resources.


With the M1, developers didn't have the *option* to use more than 5GB (until iOS 15). Same thing here.
 
That's different. After the X was announced and before it was launched, developers still had all the tools and resources they needed to make their apps compatible available to their disposal. Some people at Apple internally dropped the ball, but developers still had the resources.


With the M1, developers didn't have the *option* to use more than 5GB (until iOS 15). Same thing here.
The point is sometimes it needs time to get things into place. When I first got iPhone X there's almost *zero* 3rd party apps using the new screen real estate, whether they have tools or not is almost irrelevant if there is no result. And I had to wait almost a year for the most popular messaging app here to be iPhone X compatible. Such a good time 😓
 
I knew it was a bug.

Like I said. When Apple comes up with a name for a technology, "Retina", "TouchID", "TrueTone", "ProMotion", it means it works the same way on all devices. It wouldn't make sense for "ProMotion" to work differently on the iPad Pro than on the iPhone.
Airplay 2 kinda begs to differ, no multi-out as a system level option on macos, and magsafe is quite a bit different from previous macs to iphones and presumably whatever they introduce in the new macs this year
 
Should've been ironed out at launch and not sometime in the future post launch like the memory restriction on iPadOS on iPad Pro M1. Imagine if Nvidia launched a new GPU where you don't get 100% usability until months later.
When I got my 5700XT, it was not better than my GTX 1080. Yet after driver updates, it resulted in an average of 30% better than my 1080. These things happen....
 
The only thing that sucks about this being opt-in is that there are a lot of lazy devs that will take forever to add that one line of code or whatever it is.

How long did it take some devs to implement dark mode?
Oh wow, dark mode. Even forgot that's a thing. Tried it once, turned off and forgot.

The most interesting thing here is wether Apple provided this info to developers or not at release. If not, how can that even happen? I mean, this was the big "thing" about iPhone 13, and the info to developers that they have to explicitly state their apps want 120Hz was not there? One would think that's not something that you happen to forget with a company as big as Apple with all their love for developers. Unless you were hoping that no one would notice, or that not allowing it would make the battery last a lot longer for first testers and Apple would sneak that info into documentation without any big fanfare a few weeks after release.
Really, something smells fishy here.
 
Buy now, enjoy 120Hz “later”. When we release the documentation and fix our software “soon”.
Should developers and users have to discover this kind of known issues by themselves?. Why not properly and transparently document ceveats or known lack of support or bugs known?.
A unknown bug is one thing and hiding and purposely omitting to share information is a tooootally different issue.
 
Not that it’s a major issue for any party, but this seems counterintuitive to Apple’s best interests as this means less apps are ready for “showtime” at 13 Pro launch.

Even if a lot don’t care this must be killing a good amount of ProMotion hype.

I have to wonder this announcement is just reaching app devs now because Apple didn’t want them “leaking” the fact that ProMotion was in fact coming to iPhones this year?

Seems very late to only make this announcement post iPhone 13 Pro launch.
 
  • Like
Reactions: schneeland
So all the battery life reviews we have seen had 120hz disabled most of the time? How convenient.
It seems to be 120hz almost all the time (even in third party apps) but with some animations in 60hz. I've been using the phone for just under 24 hours and being the first time I've used a 120hz display the difference is immediately obvious, even in third party apps.
 
There are bound to be apps that blindly assume 60 Hz, which would break if it suddenly changed to 120. Making it opt-in works around that issue, although it would've been nice to provide the details to developers in advance.
Apple didn’t want developers to leak that the 13 Pro’s would have a 120Hz ProMotion display, in advance.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.