Movement I
Set the full base package
The first release carries the full picture the device needs before later over-the-air changes begin to arrive.
Cresc OTA
A steadier cadence for React Native updates.
Named for the gradual rise in music, Cresc treats over-the-air publishing the same way: smaller packages, deliberate rollout, and recovery kept within reach when a change needs to be revised.
Open-source on GitHubSelf-host friendly
Named for crescendo
Composed for careful release work.
The first native release establishes the full picture. After that, Cresc can deliver only the missing detail and let the device complete the scene locally.
Measured cadence
Publish in smaller, deliberate steps instead of treating every release as a full reset.
Light variations
Diff-based delivery keeps each update closer to a new phrase than a whole score.
Reliable return
Rollback stays close at hand whenever a release needs to settle back into place.
Incremental Delivery
Add the missing detail, not the whole canvas.
Like a variation added to an existing score, each Cresc update arrives as a measured addition to what the device already holds.
Current state
Base package present
0%
The device already holds the full portrait. The scroll only introduces the pearl, mirroring how Cresc sends the missing patch instead of re-sending the whole release.
Movement II
Send only the new detail
When the app changes, Cresc prepares a smaller patch instead of shipping the entire bundle again.
Movement III
Complete the picture on device
The client combines what it already has with the new patch, so the finished release appears with much less transfer.
In Practice
Three steps, kept in time.
Install the CLI, upload the baseline, and publish the update with the same steady rhythm each time the app changes.
I
Install the CLI
Connect your project to the publishing workflow with the Cresc command-line tool.
II
Upload the baseline package
Give Cresc the native build it compares against before later updates are published.
III
Publish the update
Bundle JavaScript and assets, then release the update through the dashboard or your CI flow.
First release
npm i -g react-native-update-cli cresc uploadIpa ios-release.ipa cresc uploadApk android-release.apk cresc bundle --platform ios cresc bundle --platform android
After the first baseline is in place, the dashboard and CLI can carry the rest of the release cycle with much less effort.