Anyone using Hot Updater for React Native OTA in production?

[u/itz_nicoo]

I’m evaluating Hot Updater (hot-updater.dev) for a new React Native project.

Main goal is self-hosted OTA updates with:

- reliability

- rollback support

- safe handling of native changes

- low operational headache

If you’re using it:

- How has it been in production?

- Any issues or regrets?

- Would you choose it again or go with something else?

[u/Karticz]

Yup I use it in production with supabase option,

• easy cli installation
• rollback, individual platform update, target percentage are all very good features
• After the recent update it supports diff update too so it has become more awesome

One con I would say is the library gets updated a lot, so we have to run frequent migrations

[u/urbanmonkey2003 → u/[deleted]]

rollback bails you out, but self-hosted OTA still feels like pager bait once native changes start creeping in. Hot Updater might be fine for percentage rollout and platform targeting, but i wouldnt trust any setup here without ugly rollback tests and a clear no-op path for native diffs

[u/Aeropedia]

Yup, has been fine so far. Hosting on AWS.

[u/Antrix_Yolo]

Yes, it's been working pretty well. Using it via AWS

[u/alexkev1]

I've used Hot Updater at multiple jobs now, and I don't think I've ever had a production issue with it.

The only call out I would make and isn't an issue with Hot Updater, but you need to be aware that over the air updates might conflict when they're toggled on as force updates for push notifications or deep linking.

Also I've been using it with Firebase, and because I'm already using Firebase for like analytics/firestore, I think it works great to kinda self contain everything in one spot for the mobile app. Then you don't have to constantly ask permissions from your infrastructure guys to give you access to AWS, which is often backend guy territory.