Hardware testing
Help test Church Remote.
Have equipment we don’t? Help us understand how Church Remote behaves on real hardware, different models and church networks.
Test with TestFlight.
- Install Apple TestFlight on the device you will use for testing.
- When enrollment is open, use the public invitation on this page. Apple checks device criteria and shows the compatible builds and available spaces.
- Accept the invitation and install an available beta. Read What to Test before using its features, and send feedback through TestFlight.
Enrollment is separate for each app and platform. A planned feature on this website is not a promise that it is included in your beta build. Public App Store releases are separate from TestFlight.
Useful coverage starts with your setup.
We’re looking for real-world feedback from people who can safely test their own authorized equipment. Useful coverage includes X32/M32 mixers, multi-M/E ATEM switchers, Resi decoders, TV models, iPhone/iPad discovery over Wi-Fi or Ethernet and Apple Watch remote controls.
These are areas of interest, not a list of confirmed beta features. We’ll confirm the models, integrations and Apple devices eligible for a particular build. We cannot promise every model or research integration works. Discovery-only support does not imply control, playback, routing or certification.
Vendor permissions and licensing still apply. NDI and Q-SYS research are not being opened by this signup. Read the integration status and compatibility and product terms before relying on a feature.
Register interest in beta testing.
Your details go privately to the Church Remote support inbox so we can coordinate testing. There is no public tester directory. This form records hardware interest; it does not enroll you in TestFlight. Use the verified public invitation above when enrollment opens.
Forms are processed by FormSubmit and delivered to support@getchurchremote.com. A spam check may open when you submit. Prefer email? Email your beta-interest details.
Already testing? Tell us what happened.
Use the existing support form to send hardware test results. Include the Church Remote version/build, equipment model and firmware, Apple device/OS, what you tested, what you expected and what actually happened. Mention whether the result repeats and whether you used Wi-Fi or Ethernet.
Keep addresses and credentials out of reports. If screenshots are useful, remove personal or confidential information before sharing them by email.
Send hardware test resultsProduct updates are a separate choice.
Want release news as well? Sign up separately for product updates. That form has its own unchecked consent box; beta interest alone never adds you to the newsletter.
Prefer the released app? Get Church Remote on the App Store. Released and upcoming features are listed separately on the integrations page.