SwiftPatch started as a Slack rant. One of us had just spent 72 hours nursing a one-character typo through App Store Review. The other was on their sixth month of maintaining a CodePush fork that predated Microsoft deprecating it.
We looked at each other and said: this is stupid. Billions of users. Eleven-figure industry. And the tooling to push a single line of JavaScript to a device is worse than git was in 2008.
There are three big reasons the problem is unsolved, not one. Let's do them in order.
The problem is not the technology
Pushing a diff to an edge cache and letting a device fetch it on next launch is — technically — not a hard problem. OTA has existed in some form since the Palm Pre. Electron apps auto-update. Web apps auto-update every page load.
What's hard is the bundle of adjacent problems that all need to be right simultaneously for OTA to be trustworthy: signed releases, cryptographic device verification, staged rollouts with automatic rollback, binary diffing that actually helps on 3G, telemetry that streams instead of batching, and a pricing model that doesn't punish you for being successful.
CodePush had four of the seven. The remaining three killed it.
“A deploy tool you can't trust is worse than no deploy tool at all. Trust is the product.”
So we're building all seven
Binary diffing. Ed25519 signing. Sub-3s auto-rollback. Staged rollouts with live audience targeting. Streaming analytics. Published pricing. And a free tier that's actually free forever, not free until you hit 100 MAU.
Join the waitlist if any of this resonates. We ship every week, and we answer every question in the Discord.