Mobile Release Notes Monitor

Compare Apple App Store and Google Play release responses. The actor normalizes versions, build/version codes, localized release notes, release dates, track status, staged rollout fractions, update priority, and minimum OS versions.

Supported Store Responses

• Apple iTunes Search API lookup responses from an app ID lookup
• Google Play Developer API track resources with releases, versionCodes, localized releaseNotes, status, userFraction, and inAppUpdatePriority
• Generic JSON arrays or structured previousReleases and currentReleases
• Simple HTML or text containing an explicit version

Apple lookup documentation: https://developer.apple.com/library/archive/documentation/AudioVideo/Conceptual/iTuneSearchAPI/LookupExamples.html

Google Play track resource documentation: https://developers.google.com/android-publisher/api-ref/rest/v3/edits.tracks

The actor compares saved prior and current responses. Google Play Developer API responses normally require caller-managed OAuth; never put credentials in an input snapshot or URL.

Example Input

{
  "targets": [
    {
      "sourceId": "example-ios",
      "sourceUrl": "https://itunes.apple.com/lookup?id=123456789&country=us",
      "appId": "123456789",
      "platform": "apple-app-store",
      "locale": "en-US",
      "previousSnapshot": "{\"resultCount\":1,\"results\":[{\"trackName\":\"Example Mobile\",\"trackId\":123456789,\"version\":\"5.3.0\",\"releaseNotes\":\"Fixed login bugs.\",\"currentVersionReleaseDate\":\"2026-06-15T12:00:00Z\"}]}",
      "currentSnapshot": "{\"resultCount\":1,\"results\":[{\"trackName\":\"Example Mobile\",\"trackId\":123456789,\"version\":\"5.4.0\",\"releaseNotes\":\"Adds offline mode.\",\"currentVersionReleaseDate\":\"2026-07-08T12:00:00Z\"}]}"
    }
  ],
  "maxTargets": 1,
  "maxReleasesPerTarget": 100,
  "includeUnchanged": false,
  "includeReport": true
}

Output

Each row contains:

• App identity: appId, appName, platform, track, and locale
• Version evidence: old/new release name, version, version direction, version-code arrays, and release dates
• Rollout evidence: old/new status, rollout fraction, update priority, and minimum OS version
• Release-note evidence: old/new text, SHA-256 hashes, and added/removed terms
• Decision fields: changeType, status, severity, score, summary, and recommendation

changeType distinguishes a new or removed release from note, status, rollout, date, and other detail changes.

Failed fetches and responses with no valid releases produce an explicit diagnostic row through diagnosticCode and sourceError.

Google Play Input Example

{
  "track": "production",
  "releases": [
    {
      "name": "5.4.0",
      "versionCodes": ["540"],
      "status": "inProgress",
      "userFraction": 0.25,
      "inAppUpdatePriority": 3,
      "releaseNotes": [
        { "language": "en-US", "text": "Adds offline mode and fixes a critical crash." }
      ]
    }
  ]
}

PPE Pricing

Event prices include Apify platform usage for the configured fixed-inclusive model.

• actor-start: $0.02000 once per paid run
• target-checked: $0.00650 per release source
• snapshot-compared: $0.00650 per prior/current comparison
• change-detected: $0.01300 per emitted change
• digest-generated: $0.05000 when digest artifacts are written
• executive-report-generated: $0.10000 when the Markdown report is written

The actor stops before additional output when the charge limit cannot cover the next paid event.

Limits

• Up to 50 app targets and 500 normalized releases per side per target.
• Apple lookup data describes the current store version, so historical monitoring requires saving prior responses.
• Google Play track resources represent active track releases; obsolete releases may not be present in later responses.
• Plain HTML and text parsing is intentionally narrow. Prefer official JSON response bodies or structured release records.