Apple shipped a feature in a beta and told you it is not shippingApple shipped a feature in a beta and told you it is not shipping

Apple seeded the first developer betas of iOS 27.2, iPadOS 27.2, macOS 27.2 and tvOS 27.2 on 16 September, two days after the 27.0 releases. iOS and iPadOS are build 24B5084k, replacing 24A435; macOS is 26B5086k; tvOS is 24K5088l.

The interesting part is not the builds. It is that the beta contains the rebuilt, Apple Intelligence Health app, and Apple's release notes say plainly that it will not be in the launch version of iOS 27.2 and will come later in the year.

This is the clearest evidence grade there is

We have written before about grading platform evidence by whether you can run it. This case is unusual because it sits in two grades at once, and Apple has told you which one to use.

You can install it. You can see the Insights tab, the readiness score, the Longevity tab, the Health Age metric. MacRumors describes working features rather than strings found in a binary. By the usual test - can you run it - this is as solid as evidence gets.

And it is still not shippable, because the vendor has said in writing that it is not in the release. A team that tests a feature, sees it working, and schedules around it has done everything right except read the note.

Working in a beta and shipping in the release are different claims, and only one of them is a date.

What to do with a feature in this state

• Test against it. That is what it is there for, and finding out now that your HealthKit writes look wrong in the new interface is worth the afternoon.
• Do not put it in a plan with a date. There is no date, and later in the year is not one.
• Tell the client it exists and is not scheduled. Hearing it from you in September is very different from hearing it from a competitor in November.
• Assume the shape moves. Features that ship late ship changed; that is usually why they were late.

Neither source names an API or a HealthKit change, so we are not going to describe one. What is documented is an application, not an interface, and the distinction decides whether there is anything for a developer to integrate with at all.

The cadence is its own signal

A .2 beta arriving two days after .0 tells you something about the release train independent of what is in it. The platform is already working two versions ahead of every user you have.

In practice that changes the advice we give about waiting. The old counsel of holding a client's minimum target until the .1 release assumed a gap of months. When the next train is already in testing before the launch-week bug reports have been triaged, the question is no longer whether to wait but which train your fix realistically lands on - and that is a question you can only answer if you are already running the beta.

Some of what is not yet in the Health app is named too: ordering labs, personalised recommendations and customised guidance are all described as coming later. A feature that is partially present in a beta is the easiest of all to over-read, because the part you tested worked.