Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Here we go with the tutti-frutti, phoney-baloney, plastic banana, good time, rock-n-roll Apple PR "leaks," this time about Apple going "all-in" on bug fixes. The problem is much bigger than can be fixed in a week because it is strongly influenced by the insistence on secrecy first and releasing everything at the same time second. Until that culture changes, expect more of the same, no mater what Apple PR "leaks."
 
  • Like
Reactions: aleksander
I wish Apple would stop with the yearly updates and stop iOS-ifying macOS. I hope they pause all new features and just fix bugs and finally work on GUI design, fit and finish. This should be an every other year thing.

Each OS should look and behave relative to the devices they are used on (desktop versus mobile) while continuing to work seamlessly together. Bring back unique shaped icons for the desktop and subtle and tasteful textures, shadows and buttons.

iOS has been 'flat' and visually the same (give or take a few widgets) for over 10 years now - far longer than the iOS style it replaced was in use. Unfortunately, everyone seems to copy Apple's design style, so frustrating and often unintuitive navigation has become commonplace. It's time to bring elegance and design back into Apple GUIs.

There is a middle-ground between leather stitching gaud and boring, lazy, flat design with tiny links, arrows, 'x' buttons, while lacking options and features - all within a sea of blank GUI nothingness in some cases. I trust Apple and their endless resources to get there for both macOS and iOS/iPadOS.
 
  • Like
Reactions: JPJones
Great so another year of small changes, and boring updates, I was hoping next year would be a complete design change and nice new features
Did you read some other story (or no story at all)?

Nowhere in the story did it say what you just said. They are going right back to feature development on it.
 
Honestly, it’s better than never, but little too late. They needed to do this a while ago.
 
I'm so confused. Why don't they have a separate development team that solely focuses on fixing bugs. Apple has the resources to support a team.
 
  • Like
Reactions: pappl
Wasn't iOS 17 billed as the "SL Release" we all wanted

Where?

That does not work. Software engineers tend to be specialists in a particular piece of software.

Folks at Apple switch teams all the time. Like, not several times a year, but certainly over the course of their careers there.

And it's certainly possible — and does happen at Apple — to have some staff on the team focus on the next release and some other staff on fixes to the current release. There isn't 100% overlap between the people working on iOS 18 and those working on iOS 17.2, or 17.1.1, for that matter.


Only a week long bug fixing sprint?!

Does anyone have any idea how Apple's development cycle work?

This is decided by the team. There is no Federighi edict on it.

And Gurman certainly does not have any idea about it, because the idea of a one-week bug fixing sprint is idiotic. You're losing velocity pulling everyone from what they're working on, and then you're only doing it for five days. Also, not every engineer's expertise is in bug-hunting. People who research prototypes for iOS 19 and beyond, or for Swift, or even for future apps. People working on Vision Pro (which has yet to see a stable release and therefore is not affected by any public-facing bugs). None of them are a good fit for "alright, boss got annoyed by some bugs, chop chop, fix 'em". That's a horrible way to run an engineering org, and given that Federighi was long a developer himself, he would know.


We were promised no new features in iOS 17

…? By whom?
 
  • Like
Reactions: jido and GMShadow
You guys seem to forget that Snow Leopard came out of the gate with a couple of pretty nasty bugs.

A serious flaw in Snow Leopard was found that would result in the full erasure of home directories when logging into the guest account (this one affected me too and almost turned me away from Apple). The bug was so widespread that Apple had to release update 10.6.2 to fix it.

In addition, there were OpenGL problems/artifacts with the Intel Integrated Graphics Models at one point (GMA 950 / X3100 for the MacBook 3,1 and 4,1), which ultimately resulted in its drop in support for OS X Mountain Lion. There was a bug for OpenType fonts too.

MobileMe was the biggest rollout mess according to many.

Noo Snow Leopard was perfect and had no bugs, how dare you. /s
 
  • Like
Reactions: JustAnExpat
I'm so confused. Why don't they have a separate development team that solely focuses on fixing bugs. Apple has the resources to support a team.
That isn't the way to do software development. It'd only create a bigger mess.
 
Now that's something new.
Not really, just been a while. Snow leopard was named the way it was because it was literally an entire release dedicated to bug fixes and stability improvements from leopard (and yes, its rollout was rough, but it became a massive improvement over leopard after those gm release issues were ironed out)

They need to do that again, not just a temp freeze but an entire release cycle where feature work is deprioritized and focus is on stability and bugs
 
“Apple's software chief Craig Federighi has been making an effort in recent years to ensure that software bugs are addressed”

Who writes this articles??? Absolutely delusional!
 
  • Like
Reactions: pappl
Because in the past it was for the most part feature complete. The keynote is the release, it is what all of the magazines and articles use. When Apple screws up, then after the fact they hedge their bets with delays on functionality for the hardware release. I must have guessed right, you really don't have the experience to comment on these issues.

The whole point of a beta is to find bugs and fix them, and allow developers to test their own apps so they have anything show-stopping fixed by the final release.

A dev beta is never 'feature complete'.
 
I can’t believe Gurman gets paid to write this drivel. And that’s assuming any of it is actually true.
 
I'm so confused. Why don't they have a separate development team that solely focuses on fixing bugs. Apple has the resources to support a team.
I tried to explain this above. It takes a long time to become familiar with a section of code and understand how it works. so teams are organized around blocks of code. Debugging code you have never seen before is really hard and times a lot of time. Mostly you just try and figure out how it works. It is a very unproductive process.

I hate car analogies but let's say you are designing a car and you have a teems that works on hydraulic brake cylinders and another that works on a wire harness When problems happen you need the specialists to look at the place where they are experts. You become the expert on a system because you worked on it for some years
 
  • Like
Reactions: crjackson2134
Opened the apple podcast app this week. Was expecting a few dozen new episodes. Instead, it started downloading 19,000 different episodes. And since there is no way to mark all as played except for going through each show manually I just deleted every show and gave up.

How can Overcast made my one man be so good. And how can Podcast made by the company that invented podcasting be so so so so so broken?
Because the people making podcast is hired, and overcast is made with love. Ez
 
I'm someone who remembers Mac OS X Snow Leopard, whose goal was improved performance, greater efficiency and the reduction of its overall memory footprint, rather than new features. I heartily endorse ALL OS developers, not just Apple, to adopt this strategy from time to time. Our digital devices become more and more swamped with features we don't want, don't need or can't figure out how to use, or just don't work right, and take up more and more memory and bandwidth. It's good to see Apple hasn't completely abandoned this practice.
 
Guess when people don’t want your updates anymore and you’ve been sued for slowing down phones, might as well eventually learn
 
We need a tick-tock cycle of cleaning up/overhauling the system performance and bugs, and adding new features. Or just hire a LOT more engineers and managers to work on improving their processes for catching bugs?

What's funny about this whole buggy debacle this autumn is in the past I feel like I would get the most random bugs that nobody else had, and this cycle I am not experiencing any of these bugs, for the most part. Only my weather widget on my watch was glitching out but it still worked most of the time when it didn't work at all for others. So strange. And with the watch battery draining bug, I only noticed a slight dip on my Ultra 2. I haven't been experiencing any of the macOS, iOS, or iPadOS bugs.
 
  • Like
Reactions: jido
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.