# Mobile Release Notes Monitor (`junipr/mobile-release-notes-monitor`) Actor

Monitor public mobile release notes, version history, update frequency, and change themes.

- **URL**: https://apify.com/junipr/mobile-release-notes-monitor.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 target checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{
  "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

```json
{
  "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.

# Actor input Schema

## `targets` (type: `array`):

Capped previous/current release comparisons.

## `sourceUrl` (type: `string`):

Public Apple lookup or authorized release-response URL fetched when enabled. Do not embed credentials.

## `appId` (type: `string`):

Apple app ID, bundle ID, or Google Play package name.

## `appName` (type: `string`):

Fallback app name for result rows.

## `platform` (type: `string`):

Store associated with the source response.

## `track` (type: `string`):

Google Play track or production for Apple.

## `locale` (type: `string`):

Fallback BCP-47 locale for release notes.

## `previousSnapshot` (type: `string`):

Prior Apple lookup JSON, Google Play track JSON, generic JSON, HTML, or version text.

## `currentSnapshot` (type: `string`):

Current Apple lookup JSON, Google Play track JSON, generic JSON, HTML, or version text.

## `previousReleases` (type: `array`):

Prior structured release records.

## `currentReleases` (type: `array`):

Current structured release records.

## `fetchUrls` (type: `boolean`):

Fetch sourceUrl only when currentSnapshot is omitted.

## `fetchTimeoutMs` (type: `integer`):

Per-request timeout in milliseconds.

## `maxTargets` (type: `integer`):

Maximum release-source comparisons.

## `maxReleasesPerTarget` (type: `integer`):

Maximum normalized release records read from each side.

## `maxTextBytes` (type: `integer`):

Maximum bytes retained for each response.

## `includeUnchanged` (type: `boolean`):

Emit release records with no detected changes.

## `includeReport` (type: `boolean`):

Write JSON result, JSON summary, and Markdown digest artifacts.

## `dryRun` (type: `boolean`):

Validate input without network requests, charges, or output rows.

## `debug` (type: `boolean`):

Enable debug logging.

## Actor input object example

```json
{
  "targets": [],
  "sourceUrl": "",
  "appId": "",
  "appName": "",
  "platform": "apple-app-store",
  "track": "production",
  "locale": "en-US",
  "previousSnapshot": "",
  "currentSnapshot": "",
  "previousReleases": [],
  "currentReleases": [],
  "fetchUrls": false,
  "fetchTimeoutMs": 10000,
  "maxTargets": 1,
  "maxReleasesPerTarget": 100,
  "maxTextBytes": 120000,
  "includeUnchanged": false,
  "includeReport": true,
  "dryRun": false,
  "debug": false
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized release change rows.

## `resultsJson` (type: `string`):

All release changes as JSON.

## `summary` (type: `string`):

Version, note, and rollout change counts.

## `markdownReport` (type: `string`):

Readable mobile release change digest.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/mobile-release-notes-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/mobile-release-notes-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/mobile-release-notes-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=junipr/mobile-release-notes-monitor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/xb2vORzc8ijy9BX6k/builds/PV22HJ3sw3c8So21L/openapi.json