Withings puts Apple Health sync behind a $99/year paywall

5 min read 1 source clear_take
├── "Paywalling Apple Health sync turns a general-purpose health device into a crippled walled garden"
│  └── top10.dev editorial (top10.dev) → read below

The editorial argues that Apple Health / Health Connect export is the critical plumbing that keeps a fitness device from becoming a walled garden — enabling data flow to doctors, training apps, and other health tools. Gating that export behind a subscription turns the Withings scale into a materially worse product than what customers thought they were buying.

└── "Withings is charging rent on an integration that should be table stakes for owning the hardware"
  ├── top10.dev editorial (top10.dev) → read below

The editorial frames the move not as charging for a new feature but as retroactively monetizing basic interoperability. The data already exists on the device and in the Withings app — the only thing being gated is the handoff to Apple's free, OS-level health store, which the editorial characterizes as rent-seeking.

  └── @johnbehnke (Hacker News, 243 pts) → view

The original forum poster, whose complaint reached HN, titled their post 'Unacceptable: Apple Health Sync is now behind a $99/year paywall for new accounts.' They bought a Withings scale, set it up on a new iPhone, and discovered the weight data would not flow to Apple Health without starting a Withings+ trial — framing this as an unacceptable bait-and-switch after hardware purchase.

What happened

Withings — the French maker of smart scales, blood-pressure cuffs, and the ScanWatch line — quietly moved Apple Health, Google Fit, and Health Connect syncing behind its Withings+ subscription for new accounts. The tier runs $99/year (or $9.99/month). Existing accounts created before the change still get the sync for free, at least today.

The discovery thread on Withings' own community forum, titled *"Unacceptable: Apple Health Sync is now behind a $99/year paywall for new accounts,"* hit the Hacker News front page with 243 points and a predictably furious comment section. The complaint is narrow and specific: a user bought a Withings scale, set it up on a new iPhone, and found that the weight readings would not appear in Apple Health unless they started a Withings+ trial. The data is already on the device. It's already in the Withings app. The only thing being gated is the handoff to the OS-level health store that Apple ships for free on every iPhone.

Withings is not charging for a feature. It's charging rent on an integration that used to be table stakes for buying the hardware. The company has not published a changelog entry or a blog post explaining the move; the forum post from an angry customer is, as of this writing, the primary source.

Why it matters

The Apple Health / Health Connect export is the one piece of plumbing that keeps a fitness device from becoming a walled garden. It's how your scale talks to your doctor's patient portal, how your watch's heart-rate data ends up in a third-party training app, how a diabetic's CGM data shows up next to their weight trend in a single timeline. Paywalling that export turns a general-purpose health device into a Withings-app-only health device, which is a materially worse product than the one on the box.

The move also lands in a specific commercial context. Withings launched Withings+ in 2021 as an optional premium tier — guided programs, deeper analytics, a human coach. For four years it was a value-add. Pulling a previously-free integration behind the same paywall is the classic SaaS maneuver of feature migration: features originally shipped as part of the hardware purchase get re-labeled as subscription features once the subscription exists. Peloton did it with the leaderboard on non-Peloton bikes. BMW tried it with heated seats. HP has spent a decade doing it with ink. The pattern is well-understood; it just hadn't fully reached the quantified-self category until now.

The HN thread's second-order anger is about the grandfather clause. On paper, existing users are fine. In practice, every veteran of this playbook knows what comes next: the free tier for legacy accounts quietly degrades, a "we're simplifying our plans" email arrives in 18 months, and the paywall closes behind everyone. Grandfathering is almost never a permanent commitment; it's a PR instrument that buys the company a quieter rollout. One top comment on HN points out that Withings' own 2017-era marketing specifically called out Apple Health integration as a reason to buy — meaning anyone who bought the hardware on that promise is now one policy change away from losing it.

There's also a competitive angle worth naming. Garmin, Oura, Whoop, and Eight Sleep all currently sync to Apple Health without a subscription. Fitbit (now Google) does it inside the Fitbit app for free. Withings is the first mainstream player to put this specific feature behind a recurring fee. If it sticks — if the churn and the HN rage don't move the needle — expect at least one of the subscription-hungry competitors to test the same move within a year.

What this means for your stack

If you're a developer building anything that reads from Apple Health or Health Connect, this is a signal to assume the data source is adversarial over time. The OS health stores were designed as a neutral integration layer, and for a while vendors treated them that way. That assumption is now dated. Any app that depends on a specific brand of scale or watch pushing data into HealthKit should either (a) support direct vendor-API ingestion as a fallback, or (b) warn users at onboarding that the sync path depends on a third party's subscription policy. The quiet failure mode — "my data stopped showing up and I don't know why" — is a support nightmare you don't want to debug six months after shipping.

If you're a buyer, the correct mental model for a connected health device in 2026 is the printer model: the hardware is a loss-leader for a subscription you may not have agreed to yet. Read the fine print on the box for the words "subscription required" near the integration you actually care about. If it isn't there, screenshot the product page before you buy — that's your evidence when the T&Cs change.

For product and platform engineers, there's a design lesson in the backlash. The feature Withings paywalled is the one that makes their device feel like it belongs to the user instead of to Withings. Users notice. The forum thread isn't angry about the price — $99 is roughly what people already pay for a MyFitnessPal Premium or a Strava subscription. It's angry about the category of thing being charged for: a data export the OS vendor made free on purpose. That distinction is going to matter more as every durable good grows a cloud account.

Looking ahead

The near-term question is whether Withings reverses, partially reverses (e.g., sync-only tier at a lower price), or holds the line and absorbs the churn. The company has not yet responded publicly to the HN-amplified complaint. The medium-term question is whether Apple and Google tighten the HealthKit / Health Connect developer agreements to prohibit paywalling the export itself — they have the leverage, and "you cannot charge users to use the OS integration they already paid for" is a defensible App Store rule. The long-term question is more uncomfortable: whether we're watching the last few years of fitness hardware that works without a subscription, or just a particularly clumsy early example of the inevitable.

Hacker News 386 pts 269 comments

New Withings Users Must Pay $99/Year for Apple Health Syncing

→ read on Hacker News

// share this

// get daily digest

Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.