Originally published in mid-2022. Updated October 2025 to reflect Apple’s later changes, including the unified developer/public beta program and expanded Feedback process. While those moves improved access, the deeper issue of how Apple listens still remains.
The work Apple’s engineers do across iOS, macOS, watchOS, iPadOS, and yes, even the tvOS crew down in the dust and cobwebs, is wearisome and worthy of praise. But that does not make the updates — or the work behind them — completely immune from criticism.
I remind myself, however, that we, as customers, view Apple as something — a creature, if you will. But a corporation is a group of humans. When we’re griping about something, we’re attacking someone’s work, something that they were proud enough to distribute to billions of individuals. That sense of connection and compassion does have a point, though — the point where mistakes start to trickle into everyone else.
I’m a genuine admirer of Craig and his entire team, and of much of the work the OS division has done in recent years. They’ve pushed the industry forward in exciting and privacy-focused ways through meaningful changes like App Tracking Transparency, Apple’s firm stance on privacy, and genuinely innovative features like Universal Control. (macOS Ventura, to my surprise, actually made Universal Control better.)
But if you compare Apple’s OS business the last three years, you see a disturbing trend — less quality for the sake of getting it done, features rushed out the door before they’re actually ready, and an unstated sense of arrogance that “Apple knows best” because it’s some kind of higher authority.
While I’ll save my commentary regarding the future of the company for another day, I’d like to point out one of the too-often-overlooked elements of Apple’s process of developing iOS, macOS, tvOS, watchOS, and iPadOS updates: betas.
The Beta Problem
Beta testing by its nature is buggy and unfinished software. Inconsistencies and bugs are the price you pay — that’s what a beta is. I don’t complain about iOS beta updates being buggy. I will complain, though, that if beta software is necessarily buggy, then beta testing should lead to cleaner, more stable releases later on.
Increasingly, that isn’t happening.
Anyone who has been paying attention to Apple or the technology world more broadly knows that recent years of iOS releases have been rocky. Features are spotty, system UI bugs are epidemic, and there is a general perception that quality has slipped.
Now, okay, Apple’s argument is that there are billions of iPhones out there in use throughout the world. The percentage of users on Twitter, Reddit, and forums that complain about bugs is not representative of most iPhone users. But when you charge more than $1,000 for what’s marketed as a premium smartphone experience, even that percentage should be heard. It’s the minimum that they should demand from a company based on the existence of devotion to the “Apple philosophy.”.
Even without full statistical account of all users, the grievance about bug-ridden iOS releases hints at something deeper — a deep-seated issue with how Apple thinks about software development and the beta testing that is meant to “help us make our software the best that it can be.”
I do believe Apple has become a bit too lean. The company is doing more than ever — and with $200 billion in cash, maybe it can — but you don’t want to put more on your plate when you haven’t yet mastered what’s there. (The fact that realityOS launches this even makes it more troubling.)
And yet, Apple’s OS teams are geniuses. The problem isn’t genius; it’s equilibrium. A mad fixation on deadlines, in combination with a fundamentally broken beta process, renders new releases insufficiently prepared for widespread use.
The Beta User Problem
I learned several weeks ago, while installing an iOS 16 beta, just how unsettlingly simple it is to do. Freakingly simple. Unbelievably simple. Apple has been outspoken in its opposition to sideloading, and it has warned that the practice could unleash “the floodgates of hell” and expose users to instability or data loss. But where is that same caution regarding unreleased system software?
Why can anyone simply download a beta profile off some public link, restart their phone, and suddenly they’re on pre-release firmware? Isn’t this just as scary — if not more so — than sideloading apps? Apple sends warnings regarding placing betas on final devices, but no one pays heed since they don’t need to.
Apple never specified how many individuals take part in its public or developer betas, but whatever the number might be, it’s safe to assume the system falls apart and is reassembled. Beta access must be more structured, more disciplined. My suggestion: scrap the beta profile entirely. Betas should be released only through a vetted registration process tied to specific devices.
For developers, that may mean registering a device as an official “iOS Test Device” before any given beta is pushed server-side. No profile, no shortcuts. It’s imperfect, but it’s a step toward a more uniform and accountable process of beta testing — one that might eliminate what I call the “TikTok crowd” of users with no idea what they’re doing.
The Not-So-Feedback App
When your Feedback app fails at its sole mission — collecting feedback — you know something has gone off course.
The pre-installed Feedback app in betas is way past due for a total overhaul. Genuine feedback, particularly for something as intricate and user-dependent like an operating system, ought to be a dialogue between the maker and user, not a monologue.
Most beta testers probablt currently give no feedback, not due to a lack of effort, but a lack of beliving it will matter. The bulk of testers hear nothing, and when their reports go into thin air, they end up not submitting anything at all. That leaves bugs unfixed and good ideas dead on arrival.
Beyond the shoddy process, the whole approach of the app reflects Apple’s rich history of thinking that “Apple knows best.” It treats beta testers like seconds — present to watch, not to act. I don’t think Apple doesn’t value its testers, but appreciation has to be shown in action.
Reporting should be easy but worthwhile. Apple needs to strike a balance between ease of reporting and amount of detail that is required to reproduce and fix an error. Right now, it is heavily weighted toward the latter — detering people from participating altogether.
Here’s my proposal: create a conversation-based feedback system, not one of solitude. A mashup of Reddit and Apple’s internal software would be amazing — a community in which beta users can post issues, others can validate them, and Apple engineers can directly respond or follow shared diagnostics.
Apple already does something the same way in-house: if several people report the same thing, it is labeled with a “More than 10 users” tag. And that idea should be out in the open. That would make it transparent, effective, and collaborative.
What offers me optimism is Craig. Craig is a bright guy. He’s Craig. And the hair.
In Hair We Trust.