<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>WearLink guides</title>
  <subtitle>Engineer-written guides on integrating wearable data.</subtitle>
  <link href="https://wearlink.io/feed.xml" rel="self"/>
  <link href="https://wearlink.io/guides"/>
  <id>https://wearlink.io/guides</id>
  <updated>2026-09-01T00:00:00Z</updated>
  <author><name>WearLink engineering team</name></author>
  <entry>
    <title>Webhooks vs polling for wearable data: rate limits, revisions and delivery</title>
    <link href="https://wearlink.io/guides/wearable-webhooks-vs-polling"/>
    <id>https://wearlink.io/guides/wearable-webhooks-vs-polling</id>
    <published>2026-09-01T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>Why polling wearable APIs fails past a few hundred users, how each vendor implements webhooks differently, and how to design an idempotent consumer.</summary>
  </entry>
  <entry>
    <title>Apple HealthKit vs Google Health Connect for developers</title>
    <link href="https://wearlink.io/guides/apple-health-vs-health-connect"/>
    <id>https://wearlink.io/guides/apple-health-vs-health-connect</id>
    <published>2026-09-01T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>Neither has a cloud API. How the two on-device stores differ in permissions, background delivery, history and what an aggregator can and cannot do for you.</summary>
  </entry>
  <entry>
    <title>Garmin Health API access: what it takes and what to do meanwhile</title>
    <link href="https://wearlink.io/guides/garmin-health-api-access"/>
    <id>https://wearlink.io/guides/garmin-health-api-access</id>
    <published>2026-09-01T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>Why Garmin data is gated behind a business agreement, what the Health and Activity APIs actually provide, and how to design so Garmin can be added later.</summary>
  </entry>
  <entry>
    <title>How to integrate wearable data into your app (2026 guide)</title>
    <link href="https://wearlink.io/guides/wearable-api-integration-guide"/>
    <id>https://wearlink.io/guides/wearable-api-integration-guide</id>
    <published>2026-09-01T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>Build vs buy, the OAuth and webhook plumbing per provider, normalisation, revisions, rate limits and a launch checklist for shipping wearable integrations.</summary>
  </entry>
  <entry>
    <title>DPDP and health data in India: what it means for your wearable integration</title>
    <link href="https://wearlink.io/guides/dpdp-health-data-india"/>
    <id>https://wearlink.io/guides/dpdp-health-data-india</id>
    <published>2026-08-20T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>What India's DPDP Act means for wearable and health data: consent, purpose limitation, data principal rights, breach duties and how to design for them.</summary>
  </entry>
  <entry>
    <title>Google Fit is deprecated: migrating to Health Connect</title>
    <link href="https://wearlink.io/guides/google-fit-migration"/>
    <id>https://wearlink.io/guides/google-fit-migration</id>
    <published>2026-08-20T00:00:00Z</published>
    <updated>2026-09-01T00:00:00Z</updated>
    <summary>Google Fit APIs are deprecated in favour of Health Connect. What actually changes — server-pull becomes device-push — and how to migrate without losing history.</summary>
  </entry>
</feed>
