Will the New Apple Health Make Other Apps Useless? What We Know So Far

The new Apple Health doesn't make every other app obsolete — but it can reduce the need for analysis-only apps in the Apple-only scenario. On September 9, 2026, Apple announced a deep redesign of the Health app, alongside the new Apple Watch Series 12 and Ultra 4: daily scores, a long-term health analysis, even connected blood testing. It's still fair to ask what this means for apps that bring multiple devices together today — FitMesh included: it depends on what you own, and on some points Apple itself hasn't been clear yet.

What Apple announced, and when it's actually arriving

First important distinction, often confused: Apple has announced the availability of iOS 27 and watchOS 27 starting September 14, 2026, but the redesigned Health app is a separate, different thing, not yet available. Apple explicitly states it's coming "later this year" (in 2026), initially in U.S. English only, with more languages to follow — no precise date given. Source: Apple Newsroom — Apple advances health and fitness capabilities using Apple Intelligence, September 9, 2026.

According to what Apple has presented, the redesigned app requires an Apple Intelligence-enabled iPhone or iPad to be used at all — not just for individual features. The Apple Watch requirement, on the other hand, varies by feature: Health Age, for instance, requires "Apple Watch" in general, with no specific model named. Some new-sensor features (see below), instead, specifically require Series 12 or Ultra 4.

Insights, Longevity, Health Age, Readiness: four different things

These terms overlap in Apple's communication, but they mean different things. Insights is a tab for the day-to-day view: it shows a summary that updates throughout the day covering heart, sleep, readiness, fitness, vitals, and cycle tracking, plus a "For You" section with personalized recommendations. Longevity is a separate tab for the long-term view: it analyzes longitudinal data on heart health, sleep, mental wellbeing, movement, metabolic health, hearing, and nutrition. Health Age is a score inside the Longevity tab, not a tab of its own: Apple describes it as using "Apple Watch data to show how your metrics are tracking relative to your chronological age", factoring in VO2 max, resting heart rate, sleep, and HRV, plus lab data users can add manually (A1c, LDL). Readiness is a daily 0-10 score (Recover / Pace Yourself / Ready / Go For It), calculated on the Watch from recent activity, training load, vitals, and sleep score, then surfaced in the Insights tab. Sources: Apple Newsroom — Apple advances health and fitness capabilities using Apple Intelligence and Apple Newsroom — Introducing Apple Watch Series 12, with the all-new Health Sensing System, September 9, 2026.

What we still don't know

Speaking about the Longevity tab as a whole, Apple writes that users can see "what's shaping their long-term health based on data from iPhone, Apple Watch, AirPods, and clinical health records, as well as third-party apps and devices." It's the only explicit mention of third-party data in the entire announcement — but it refers to the Longevity tab in general, not specifically to how the Health Age algorithm is calculated, which the same announcement describes as based on "Apple Watch data." Apple doesn't clarify the link between the two sentences: citing third-party data in the overall Longevity vision doesn't prove that data feeds Health Age, Readiness, or any other specific algorithm — this stays an explicitly open question, not a fact resolved either way. The one precisely stated exception concerns the VO2 max estimate test, for which Apple explicitly allows "a third-party heart rate sensing device" too, alongside Apple Watch and AirPods Pro 3.

On the technical side, Apple's developer documentation doesn't yet resolve the doubt: checking the full index of HealthKit types (`HKQuantityTypeIdentifier` and `HKCategoryTypeIdentifier`) and the official changelog on September 11, 2026, no identifier for Readiness, Health Age, the Longevity tab, or Sleep Score is present. The latest HealthKit changelog entry is still dated June 2026. One partial exception: a new real identifier, `heartRateVariabilityRMSSD`, has appeared, but with no published description — declared in the SDK, not yet documented in prose, and it's unclear whether it corresponds to what Apple calls "Recovery HRV." Source: Apple Developer — HealthKit, type index and HealthKit changelog, checked September 11, 2026. Without a public API, there's currently no evidence that Readiness or Health Age can be read by a third-party app — nor that they never will be: it's a state of affairs to check again once (and if) fuller documentation arrives, not a fact to bet on now.

What FitMesh already does today, verified in the 3.10.0 code

Unlike features that have been announced but not yet released, this is verifiable: in the public 3.10.0 release, on iPhone FitMesh reads — with the user's authorization — samples of the supported HealthKit types (steps, heart rate, sleep, SpO2, calories, weight, and others), without limiting itself to the Apple Watch source: reading doesn't filter by source. When arbitrating between multiple sources, it explicitly recognizes dozens of third-party app and device source names (Samsung Health, Garmin, Fitbit, Amazfit, Huawei, Polar, Oura, Whoop, Suunto, the Colmi ring, and others) — not a direct connection between FitMesh and those manufacturers, but data those same apps write into Apple Health, which FitMesh then reads from there. For the full mechanism, including what the bridge does NOT do, see smart ring data in Apple Health.

On the writing side, always on explicit opt-in (off by default) and never in real time, FitMesh can send steps, distance, and active calories to Apple Health (only the gap missing from what's already there, never a sum), plus resting heart rate, SpO2, and weight (but only if no data already exists from another source that day). It never writes HRV — the cloud calculates RMSSD while HealthKit on iOS exposes SDNN, a different metric, and writing it would produce a wrong value — and sleep is currently disabled pending a fix for a known issue. There's no historical write backfill: only the current day. For how to export your data FROM Apple Health instead (native XML, CSV for your doctor, or a web dashboard), see how to export Apple Health data.

Three practical scenarios

• •Apple-only (iPhone + Apple Watch, no other device): this is the scenario where the new Health app, once it arrives, will likely already cover most of what you need natively — Insights, Readiness, and Health Age exist specifically for this use case. Honestly, this is the scenario where FitMesh adds the least.
• •Mixed ecosystem (Apple alongside a non-Apple device — a Garmin, a Samsung Galaxy Watch, a smart ring): here the difference stays clear. The redesigned Health app, based on what's been presented so far, analyzes your data to give you insights — it doesn't describe a mechanism for bringing together and deduplicating heterogeneous sources the way FitMesh does today.
• •Switching platforms (for example from Android to iPhone, or the other way around): the history FitMesh has already collected stays tied to your account, not to the physical device — regardless of which native Health app you use after the switch.

The verdict, in four layers

Separating what Apple has announced, what's already documented in the API, what we still don't know, and what FitMesh actually does today: once available, Apple Health will become much more capable and may reduce the need for some analysis-only apps. It won't, however, automatically replace tools that connect different devices, sources, and platforms. The first layer (the announcement) is ambitious but not yet verifiable in public use. The second layer (the API): as of September 11, 2026 we identified no documented public HealthKit API for Readiness or Health Age, and FitMesh doesn't claim support for either today. The third layer (open questions) is mostly about whether and how data from non-Apple devices will feed into these scores: we don't know, and we're not writing as if we did. The fourth layer — the only one verifiable with certainty today — is about roles: Apple Health is the Apple ecosystem's archive and analysis of data that reaches HealthKit; FitMesh, in its public release, is a cross-platform, account-based dashboard that already brings Apple and non-Apple sources together in one place, with an optional bridge to some supported metrics. These are distinct roles, not necessarily in competition.