Apple is changing how it develops its software to cut down on bugs

“The initial release windows of both iOS 12 and iOS 13 saw users complaining about a plethora of bugs both major and minor. Apple has plans to mitigate this problem when iOS 14 launches next year, according to sources who spoke with Bloomberg,” Samuel Axon reports for Ars Technica:

A major factor contributing to iOS 13’s rough launch window was the fact that many Apple developers were making daily or weekly commits of new features at varying levels of readiness and quality, and those features were enabled by default regardless of their readiness. This meant that test builds were often unusable for stretches of time due to one problematic feature or another, which limited the amount of time testers spent with the software.

Under the new methodology, new test builds of Apple’s future operating systems will turn certain features deemed to be buggy or to cause usability issues off by default. Testers will be able to opt-in on a feature-by-feature basis in many cases, reducing the likelihood that they will be working with “unlivable” builds.

The change in approach was directed by Craig Federighi, Apple’s head of software engineering, and was announced during an internal meeting. And this would also apply to Apple’s other operating systems such as macOS, watchOS, tvOS, and iPadOS.

MacDailyNews Take: Hopefully, this will mitigate bugginess in Apple’s software and operating system releases. We’re dealing with a pretty major one in macOS Catalina right now: Once our new 16-inch MacBook Pros go to sleep (lid closed, running dual external displays via DisplayPort) they won’t wake up without having to open the lids and force them to reboot. It’s not a fun bug with which to deal. We’ll next try with lids open (three displays, yay) and see how they deal with waking up from Sleep. [UPDATE: 4:20pm ET: Lid open method does not prevent waking up, but the external displays lose their resolution settings. So, it’s still buggy, just in a different way.]

Oh, here are some 16-inch MacBook Pro benchmarks we ran earlier:


  1. I’m sorry, but I am an independent, 1 person apple developer. I currently have over 10 apps in the iOS store, and only ONE app has had ONE error in the over 10 years that I have been doing this.

    Having bugs and errors in an app seems to say to me that Apple needs much better quality control AND better ways (and testers) to test any new and current apps before they hit the streets, and Apple needs to STOP letting the public be beta testers and leave it to the professionals – its developers in-house and for those who are paying for the access.

    1. Yeah, things were better when we just had the AppleSeed teams TBH.
      We work hard for zip, nada, zero and many if not most of the group are amazing talents and even dev’s too.
      When one files lots of BR’s and they get ignored, it’s deflating – esp when they get released and you’ve filed them over and over.
      At a certain point, you just stop.

  2. 13’s biggest problem is the obsession with features features features features features features, why would you be surprised that there are bugs bugs bugs bugs bugs? Apps that dont open on whatever is supposed to be the “home page” on and on Thinking of going back to 12, such as it is.

    1. Meanwhile, an elemental, very observable and cause for significant unproductively loss in iOS remains after the latest iOS release….

      A “wild cursor” gives “select” option when not wanted, the cursor needed to edit text is elusive until in shows itself in its own time and placing it precisely is is a crap-shoot.

      The problem was evident (per my experience) since the 1st release of iOS 13 and remains up to now. Maybe I’m the only one experiencing this confounding issue, but if not, its presence up to know shows it’s a small issue in comparison to others and, or the quantity of fixes are so great, this is not a priority.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.