The limit helps participants focus, reduces low-effort feedback, and discourages bulk browsing of other people's products.
Use the provide an App Store link for testing form. It asks only for a live App Store link and test instructions. It does not upload code, project files, builds, credentials, or private material.
No. Maintainers create and match tasks manually, so timing depends on the number of participants and available apps.
You need a GitHub account to join, claim a test, and submit feedback. No separate Co-op account is required during the pilot.
We're starting with a small peer-testing group of up to ten iOS developers. People will join in small waves: four in the first wave, followed by smaller waves after the previous group completes its initial tests.
No. The community only collects beta-testing, bug, usability, and product-experience feedback.
Not during this phase. We only accept apps already released on the App Store and suitable for public testing.
The first phase uses public App Store links so tasks are stable, visible, and easy to access. TestFlight builds may expire or change, and private invitation links can grant access to unreleased software. We do not want private access links or confidential builds in public GitHub Issues.
A released app that also has a TestFlight build should be tested through its public App Store listing during this phase. In a future phase, we may support public TestFlight beta links through a separate workflow. Private invitation links and invitation codes will not be posted publicly.
Negative feedback is allowed. If the tester completed the task, remained respectful, and provided specific observations, confirm completion. If necessary information is missing, ask only for that information.
The pilot primarily serves iOS developers. A tester with a compatible device who is willing to provide careful feedback may also apply.