Movement I
Hold the full base
The first release stays on device as the complete base, so later patches can remain much smaller.
Cresc
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 full native release establishes the base. Every later update can arrive as a smaller addition, shaped only to the detail that changed.
Small variation, same score
Cresc keeps the original release close, then lets each later patch arrive as a measured variation rather than a full repeat.
Incremental Delivery
Add the missing detail, not the whole canvas.
The missing change is carried into the existing app and set in place locally, instead of replacing the whole package.
App Updated!
Movement II
Drop only the new pearl
When something changes, Cresc lifts just the missing part instead of repeating the whole bundle.
Movement III
Set it in place locally
The client clicks the new patch into the existing base, then confirms the update in place.
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 releaseproduction lane
release@studio~/crescendo-app$
After the first baseline is in place, the dashboard and CLI can carry the rest of the release cycle with much less effort.