Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Some find it more pleasant, but, no, there’s insufficient evidence that it’s actually better for the eyes.

At night it's 100% easier on my eyes than a white background.

Is that the case for everyone or "better"? I don't know but my eyes are taking advantage of it.
 
  • Like
Reactions: clavain
It is dark. It lessens eye strain.
Actually it increases eyestrain. When a screen is bright white your iris closes more and as a result your eyes have more depth of field. With more depth of field focussing becomes a lot easier and as such reduces eyestrain!
 
Looks like a number of you really stuck your foot in your mouths since Public 13.1 is out.. guess you all don't know as much as you think you do, just saying.
 
‘I only use my iPad in landscape, unless I’m playing a game that requires portrait. Thankfully I haven’t experienced any of the keyboard issues. I’ve never tried using swipe. The dark mode toggle would freeze in settings but that was resolved for me since public beta 3.

Digging deeper, the issues seems to be isolated to Facebook Messenger. I guess its an app issue and not iOS. I don't seem to have this mail issue everyone is complaining about. I do have 3 different mail providers I'm using and all work well.
 
Releasing 13.1 beta before releasing 13.0 GM, on the same profile as 13.0, is all the proof you need. If that doesn't make it clear to you, then you just don't want to see it I guess.

A minor version increase (like a .1) is meant to be a target for app developers. It indicates there will be new functionality for apps that are targeting 13.1.

A maintenance releases (like 13.0.1) would be for bug fixes. It is not out of the question that the release date version will be 13.0.1, or that it will roll out before 13.1. The operating system (13.0) has to get loaded onto the phones well before they arrive to customers.

FWIW, it is by far more likely that Apple has a 13.1 because they will not release any more developer/public betas of 13.0 before GM.

Apple historically has stopped iOS betas around this time so they have time to integrate and test support for new hardware (out of the prying eyes of people like Guilherme Rambo).

However, they typically have delayed 13.1 betas until after they have had the iPhone keynote, because 13.1 will also contain any SDK changes needed to support new hardware features - things like when they added FaceID, added new gestures for added an extra camera, added haptic feedback support, and so on.

13.1 has no SDK changes, though. So, they either the existing 13.0 SDK already contains everything they will need to expose any new hardware functionality to apps, or they plan to merge those SDK changes in a later beta.

My guess is that they are tired of overpromising releases and then having features lagging (even in cases like the EKG of the watch, where they had no choice due to slow regulatory approval.). So they are starting the 13.1 process earlier to try to get these software features to customers more quickly.
 
  • Like
Reactions: John Yester
anyone else seeing the fast battery drain on the apple watch again with 13.1? was full charge and then an hour and a half later I am down to 89% already on the watch...
 
anyone else seeing the fast battery drain on the apple watch again with 13.1? was full charge and then an hour and a half later I am down to 89% already on the watch...
I charged up my watch yesterday morning and it was dead this morning when I woke up.
 
At the time of my post, the story hadn't gone up.

It went up four hours before your post. :p

upload_2019-8-29_18-46-12.png
 
If 13.1 were a different beta, it would have required a new profile to be issues.

I wouldn’t be surprised at all that a .1 release, from now on, represents the GM release and that the final release after the Apple event will be labeled 13.1.

This makes the most sense.
 
If 13.1 were a different beta, it would have required a new profile to be issues.

I wouldn’t be surprised at all that a .1 release, from now on, represents the GM release and that the final release after the Apple event will be labeled 13.1.

This makes the most sense.

Sounds like the GM is already done, and remember  needs to have something ready to get onto the new iPhones they’ll be releasing soon. I’d be shocked if they release the GM as 13.1.
 
If 13.1 were a different beta, it would have required a new profile to be issues.

I wouldn’t be surprised at all that a .1 release, from now on, represents the GM release and that the final release after the Apple event will be labeled 13.1.

This makes the most sense.

It makes no sense to me. If 13.0 isn’t meant to ship, they can just call 13.1 13.0 instead.

What might be the case is that 13.0 will only ship for the 2019 iPhone models, as some have suggested. I don’t entirely buy that either, though. Do the issues people are seeing not affect the new iPhones? They probably do, so why not just ship them with a build of 12.x and postpone 13.0 altogether?

I’m still mostly inclined to believe that 13.0 will ship as usual, but that Apple wants beta feedback to already focus on 13.1.
 
  • Like
Reactions: CNebs
Ok, my bad beta 2 of 13.1, since early betas are usually on a 2 week cycle. There fixed it for you since he did say 13.1 *is* the GM.

That’s also not what I said - but I won’t waste my time arguing with you, since you are more concerned about protecting your own narrative, than in actually thinking this through.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.