cresc.dev valid

Cresc

React Native OTA updates with delta patches, rollback safety, CI/CD publishing, and migration paths for CodePush and Expo Updates teams.

For agents: Cresc: open-source-core OTA update service for React Native with delta patches, rollback safety, CI/CD publishing and CodePush/Expo migration docs.

react nativeota updatescodepush alternativeexpo updatesdelta patches

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T22:56:07.258Z. Cached copy · Source on cresc.dev

# Cresc

> React Native OTA updates with delta patches, rollback safety, CI/CD publishing, and migration paths for CodePush and Expo Updates teams.

## CodePush & Expo Alternative

- [Cresc as a CodePush & Expo Updates alternative](/codepush-alternative.md): Cresc gives React Native teams a modern CodePush and Expo Updates alternative with massive price savings, delta OTA updates, rollback safety, CI/CD publishing, and self-hosting flexibility.

## Documentation

- [Introduction](/docs/intro.md): Cresc is an open-source-core OTA update service for React Native: delta patches, rollback protection, release monitoring and a CodePush/Expo Updates migration path.
- [Install & Use Skills](/docs/skills.md): Install the react-native-update AI Skill so Claude Code, Cursor or Codex can integrate Cresc OTA updates into your existing React Native project automatically.
- [Installation & Config](/docs/getting-started.md): Install react-native-update and configure iOS, Android and HarmonyOS native projects to start shipping React Native OTA updates with Cresc.
- [Code Integration](/docs/integration.md): Integrate Cresc into a React Native or Expo app, choose update strategies, and build a custom OTA update UI with useUpdate.
- [Publishing Hot Updates](/docs/publish.md): Publish React Native hot updates with Cresc: upload native baselines, build and publish OTA bundles, bind versions to native packages, and roll out gradually.
- [API Reference](/docs/api.md): Cresc JavaScript API reference for react-native-update: client options, checkUpdate, downloadUpdate, switchVersion, useUpdate hooks and update lifecycle events.
- [Native Configuration and Updates](/docs/native-api.md): Configure and trigger Cresc OTA updates from Android, iOS, and HarmonyOS native code with react-native-update v10.59.0 or later.
- [API Key](/docs/api-token.md): Create Cresc API keys to publish React Native OTA updates from CI/CD pipelines like GitHub Actions, GitLab CI and Jenkins, and manage key scopes safely.
- [MCP Server](/docs/mcp.md): Connect Cresc to Claude, Cursor or your own agent with the read-only MCP server to inspect apps, versions, rollouts and update health from your AI client.
- [CLI Tools](/docs/cli.md): Cresc CLI reference (react-native-update-cli): bundle, publish and upload native packages, manage apps and versions, and automate React Native OTA releases.
- [Analytics](/docs/analytics.md): Follow React Native OTA releases through traffic, version funnels, activation timing, regional reach and failure diagnostics with Cresc.
- [JS Error Monitoring](/docs/errors.md): Built-in JS error monitoring for React Native OTA releases: Cresc groups exceptions by version and restores minified stacks via archived source maps.
- [Brownfield Integration](/docs/brownfield.md): Integrate Cresc into Android apps that consume React Native through @callstack/react-native-brownfield AARs.
- [Best Practices](/docs/bestpractice.md): Best practices for Cresc React Native OTA updates: shrink ip
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=cresc.dev · GET /v1/domain/cresc.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for cresc.dev:
1. POST https://agentwebmap.com/v1/sites/cresc.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://cresc.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/cresc.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/cresc.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.