Resting Signal

Your Fitbit data, read properly.

Your health data is fetched straight from Google to this device and analysed here. It is never stored on a server — this app has no database and no account. The only thing that touches the server is the login handshake, because Google requires a client secret that a browser can't safely hold.

Checking this deployment’s configuration…
  1. Create a Google Cloud project

    Fitbit’s developer portal has closed. The Fitbit Web API is now the Google Health API, and apps are registered through Google Cloud.

    Open developers.google.com/health/setup and use the Enable the API and get an OAuth 2.0 Client ID button. When it asks:

    Where are you calling from?
    Web serverGoogle has no browser-only client type that can hold a refresh token, which is why this app ships a small login endpoint of its own.
    Authorized redirect URI
     Must match exactly, including the trailing slash. Google’s own instructions suggest google.com here — use this instead.

    At the end you are given an OAuth 2.0 Client ID and a Client Secret. Keep that tab open — you'll need both in step 3.

  2. Allow your own account, and pick the data

    A new OAuth client starts locked down. Three things to set, all in the Google Cloud console for that project:

    Audience → Test users
    Add your own Google addressUntil you do, Google refuses the login with “access denied”. It's the single most common reason this fails.
    Data Access → Add or remove scopes
    Search “Google Health API” and tick these four googlehealth.activity_and_fitness.readonly — steps, zone minutes, VO₂ max
    googlehealth.health_metrics_and_measurements.readonly — HRV, resting HR, SpO₂, weight
    googlehealth.sleep.readonly — sleep stages and timing
    googlehealth.profile.readonly — your age, for reference ranges
    Audience → Publishing status
    Publish appWorth doing. While the app sits in “Testing”, Google expires its refresh tokens after 7 days and you would have to reconnect every week. Published-but-unverified is fine up to 100 users; you are one.
  3. Store the credentials on your own deployment

    Run these two commands, from the folder this app lives in. Each one prompts you to paste a value — the Client ID for the first, the Client Secret for the second.

    npx wrangler pages secret put GOOGLE_CLIENT_ID --project-name resting-signal npx wrangler pages secret put GOOGLE_CLIENT_SECRET --project-name resting-signal

    These are stored as encrypted Cloudflare secrets on your own account. The secret is only ever read server-side by the login endpoint — it is never sent to the browser, and it is not in the source code.

    After setting them, redeploy once so the new values take effect, then reload this page.

  4. Connect

    Google will ask which data to share. Anything you decline simply leaves the matching section of the app empty.

    You will see an “unverified app” warning. That is expected — it is your own app, registered to your own account, and it only ever asks for read access.

Add it to your home screen

In Safari, tap the Share button, then Add to Home Screen. It then opens full-screen with no browser chrome, like any other app. Do this after connecting, so your login carries over.

Today