Dark Mode is not an easy on/off switch though. A TON of design retooling has to happen for dark mode to be usable.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?
Yes and no.Dark Mode is not an easy on/off switch though. A TON of design retooling has to happen for dark mode to be usable.
Dark Mode is not an easy on/off switch though. A TON of design retooling has to happen for dark mode to be usable.
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.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.
You’re a bug, I’m a bug we’re all bugs. I don’t know I’m bored 🙃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.
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.I remember when iPhone X launched some Apple own apps couldn't even take advantage of the new screen ratio. This thing happens.
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 😓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.
How do you know that? Did I miss something in the article?So all the battery life reviews we have seen had 120hz disabled most of the time? How convenient.
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 yearI 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.
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....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.
Most of the things people did in those tests were using native apps which weren’t affected by the issue… sooooooSo all the battery life reviews we have seen had 120hz disabled most of the time? How convenient.
Oh wow, dark mode. Even forgot that's a thing. Tried it once, turned off and forgot.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?
Nope affects native Apple apps too:Most of the things people did in those tests were using native apps which weren’t affected by the issue… soooooo
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.So all the battery life reviews we have seen had 120hz disabled most of the time? How convenient.
Apple didn’t want developers to leak that the 13 Pro’s would have a 120Hz ProMotion display, in advance.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.