react-native-code-push VS capacitor-codepush

Your testing team is using AppCenter.

Appcenter will allow you to build your app for iOS and install on your device without submitting to the App Store. https://appcenter.ms/

I used expo-updates with a CI script to push updates. CodePush is also a good alternative.

We've been using app center for build distribution (https://appcenter.ms/)

But, https://appcenter.ms/ and others like it are already available with generous free tiers and a lot more features (which you don't have to use, but can grow into), not to mention GitHub actions as others have noted. Does this advantages over existing, standard solutions?

There are lots of choices. Google android device testing. Offhand https://appcenter.ms comes to mind.

you don t need a mac, use microsofts app center to build it. https://appcenter.ms

I've heard good things about App Center from Microsoft https://appcenter.ms/

Don’t muck with automating simulators, it’s a PITA: we used https://aws.amazon.com/device-farm/ and it was ok. This was pretty ok: https://bitrise.io As much as I hate Microsoft, https://appcenter.ms was workable, but required the most calories and was slow.

NB: Using Capacitor in practise means bundling your website inside the app, NOT loading it on demand (via a url). That is the recommended option from Capacitor’s creator Max Lynch, since if not: "Apple will likely reject your app since it is not “self-contained.". To make it self-contained, you can do a NextJS static export, for example. Sadly, for distribution, this means going through the App Store process, and asking clients to update their app for every code change (many will thus be out of date). Unless you use a service such as CodePush for Capacitor. Never mind the weirdness of using a code distribution tool for native apps, just to serve users with fresh HTML, CSS and JS...