Romi ships first over-the-air updates to push fixes without App Store review

Romi turns on over-the-air updates

The team behind the Romi app has switched on over-the-air (OTA) updates, allowing certain changes to reach users directly instead of queuing behind Apple's App Store review. The news arrived in the inaugural post of a devlog series on dev.to, where the team publishes under the handle romiadhd.

According to the post, OTA delivery is something most apps have used for a long time, but it is new ground for this team. Previously, even a minor correction had to clear Apple's reviewers before anyone could receive it. That delay is what motivated the build.

A homegrown pipeline built on Capgo

Rather than signing up for another managed service, Romi assembled its own delivery stack from Capgo plus a content delivery network. The team jokes that adding one more subscription did not sound appealing, so it wired the pieces together itself.

Capgo is a live-update tool built around Capacitor, the framework that packages web code inside native iOS and Android shells. Choosing it indicates Romi follows that hybrid pattern: the app's logic ships as web assets rather than being compiled into the native binary, which is exactly what makes OTA updates feasible. The post admits the finished setup looks obvious in hindsight, even though the path to that point was less so.

How OTA updates sidestep the review queue

The mechanics behind this are well established. Hybrid apps built with tools like Capacitor or React Native run their screens and business logic from a JavaScript bundle. Because that bundle is interpreted at runtime rather than baked into the compiled binary, a new version can be fetched from a server and swapped in. Apple's review guidelines allow apps to download interpreted code only in narrow circumstances, and update services operate inside that allowance; changes to native code, permissions, or the app binary itself still require an ordinary reviewed release.

The payoff is latency. A reviewed App Store release can take hours or days, while an OTA push reaches users shortly after upload. For a small bug, such as a broken layout, a misfiring notification or a bad API endpoint, that difference decides whether the fix lands this week or the next.

Romi is not alone in pursuing this. Microsoft retired its App Center CodePush service in 2025, and teams that depended on it migrated to alternatives such as Capgo and Expo Updates, which has turned self-assembled update pipelines into a routine project.

Why it matters

App review is one of the biggest sources of friction for small mobile teams, and Romi's post is a compact example of the trade: invest in delivery infrastructure once, then ship corrections at web speed while saving the review queue for changes that genuinely require it. The choice to own the plumbing, pairing a CDN with an update tool, also reflects a wider preference among small teams for predictable costs over yet another SaaS line item.

The other side of the deal is responsibility. Code shipped outside the store means the team itself must handle version skew, staged rollouts and emergency rollbacks, with no review gate as a safety net. Notably, the post is the first entry in a planned series and closes with a question to readers about which habits their own teams adopted late, a small act of shipping in public that pairs naturally with shipping faster.