HELPERG (opens in a new tab) Ecosystem

WebmasterID logoWebmasterID
Menu
Changelog

What shipped, in order

Operator-facing release notes for WebmasterID Core + Agent. Newest first. The current named version is Mobile SDKs 1.3.0 / 0.3.0 / 0.4.0.

Read Mobile SDKs 1.3.0 / 0.3.0 / 0.4.0 →Connect Claude (MCP)
Releases

Every release that actually shipped

Built incrementally with operator feedback. Review-first AI workflows. No fake roadmap promises here — only work that already landed in production.

Mobile SDKs 1.3.0 / 0.3.0 / 0.4.0
Analytics

Automatic delivery on iOS and Android

The native SDKs now deliver events on their own, the same way on iOS and Android: about 5 seconds after the first queued event, when the app goes to the background, and after the next launch for anything left. An iOS app no longer needs to call flush() to be measured.

  • iOS SDK 1.3.0 (Swift Package Manager), Android SDK 0.3.0 (webmasterid.com/sdk/maven) and webmasterid_flutter 0.4.0 (pub.dev). Same public channels, no private repository.
  • One armed delivery about 5 seconds after the first queued event; later events join it and never postpone it. The app goes to the background: delivered at once, best effort.
  • After the next launch, anything an earlier launch left is delivered once the consent decision is in force — no flush(), no call from your app.
  • + 3 more — see the release page
Read release notes →
App analytics
AnalyticsCore

iOS, Android and Flutter SDKs, and Apps reports

WebmasterID now measures iOS and Android apps: public SDKs, consent-first events and five Apps reports beside your website reports, in the same workspace.

  • iOS SDK 1.2.0 from Swift Package Manager, Android SDK 0.2.0 from the Maven repository at webmasterid.com/sdk/maven, and webmasterid_flutter 0.3.0 from pub.dev. No private repository or access token.
  • Apps reports in the dashboard: Overview, Events, Conversions, Retention (beta) and Attribution, next to the Web reports.
  • Consent first: nothing is queued or sent until the app passes the user's decision, and the server refuses advertising identifiers.
  • + 3 more — see the release page
Read release notes →

Subscribe via Atom or JSON Feed. Both are generated directly from the typed release registry.

Trust posture

How we ship

A short, honest note on how releases land and what stays out of them.

  • Every entry above corresponds to a real merge into the shipping branch. No dates are invented.
  • MCP access is read-only by default. Write tools, if they ever ship, will land behind their own RBAC permission and a separate audit category.
  • Operator approval remains required for every Agent / Claude change — no autonomous deploy, no auto-merge.
  • Privacy posture is unchanged across releases: no third-party cookies, no fingerprinting, no raw IP storage.
  • We do not claim certifications, SOC2 status, uptime percentages, or customer counts on this page.
Changelog · WebmasterID