Testez chaque PR sur de vrais appareils
Oubliez les attentes TestFlight et le chaos des channels beta. Créez un channel aperçu pour chaque Pull Request et laissez votre équipe tester sur de vrais appareils - en secondes.
Le problème
Le problème TestFlight
Workflow traditionnel
Developer Opens PR
Code is ready for review. But before anyone can test it, you need to build and upload to TestFlight.
Build and Upload
Build the app locally or in CI. Archive it. Upload to App Store Connect. Wait for processing. 15-30 minutes minimum.
Distribute to Testers
Add testers if they're not already in TestFlight. Send invites. Wait for them to accept. Explain how to install.
Test the Wrong Build
Testers download the build. Dev pushes a fix. Now everyone needs to repeat steps 2-3 to get the updated build.
Des heures perdues pour chaque review de PR
Vrai coût par PR
15-30 minutes
Traitement TestFlight
Temps d'attente moyen pour TestFlight
67%
QA bloquée
Temps que la QA attend pour chaque build
$340/PR
Les coûts cachés de l'attente
Productivité perdue à attendre
La solution
Channels aperçu PR
Channels aperçu automatiques pour chaque Pull Request
Developer Opens PR
CI automatically builds the app and creates a Capgo channel named after the PR number.
Automatic
Bundle Uploads
The built bundle uploads to Capgo in the background. No processing delay.
< 30 seconds
Tester Switches Channel
Tester opens the app, switches to the PR channel, and gets the build immediately.
< 10 seconds
Test and Approve
QA tests on real device. Dev pushes fixes. Tester immediately gets updates. No reinstall needed.
Instant iteration
name: PR Preview
on:
pull_request:
types: [opened, synchronize]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup & Build
run: |
npm ci
npm run build
# Create a channel named after your PR
- name: Create PR Channel
run: npx @capgo/cli channel add pr-$${{ github.event.pull_request.number }}
# Upload the build to that channel
- name: Upload to Capgo
run: npx @capgo/cli bundle upload --channel pr-$${{ github.event.pull_request.number }}
# Post a comment with the test link
- name: Comment on PR
uses: actions/github-script@v7
with:
script: |
github.rest.issues.createComment({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: $${{ github.event.pull_request.number }},
body: '📱 **Test this PR on device:**\\n\\nOpen your app and switch to channel: `pr-$${{ github.event.pull_request.number }}`'
})Temps de configuration
Comment les testeurs changent vers votre build PR
Menu secouer (zéro code)
Activez le geste de secousse intégré. Les testeurs secouent leur appareil pour ouvrir un menu affichant tous les canaux disponibles.
// capacitor.config.ts
CapacitorUpdater: {
shakeMenu: true // Enable for testing
}Sélecteur dans l'app
Créez une interface personnalisée pour changer de canal. Parfait pour un écran de paramètres développeur dans votre app.
// Switch channel from your app
import { CapacitorUpdater } from '@capgo/capacitor-updater'
await CapacitorUpdater.setChannel({
channel: 'pr-123'
})Cas réel
Comment ça marche
TechStartup
SaaS
TechFlow's mobile team was shipping 15-20 PRs per week. Each PR needed testing by QA before merge. With TestFlight, their QA lead estimated they spent 60% of their time waiting for builds instead of testing.
The real pain came during crunch weeks. When multiple PRs needed testing simultaneously, QA had to constantly reinstall different TestFlight builds. Testers got confused about which version they were running. Bugs got reported on already-fixed code.
After implementing Capgo PR Preview, their QA team could switch between any PR in seconds. No reinstalls. No confusion. No waiting. Their average time-to-merge dropped from 2.3 days to 0.6 days.
80% de reviews PR plus rapides
"Les channels aperçu PR ont réduit notre temps de review de plusieurs heures à quelques minutes. Game changer."
— Sarah K., Lead Developer
Conçu pour les équipes
Chaque rôle bénéficie des aperçus instantanés
Ingénieurs QA
- Test any PR on your device in seconds
- Switch between PRs instantly to compare behavior
- No more confusion about which build you're running
Chefs de projet
- Review features before they ship
- No technical setup - just tap a link
- Provide feedback directly on the PR
Développeurs
- Get QA feedback before your context switches
- Push fixes and testers get them instantly
- No more 'waiting for build' blockers
La différence
Traditionnel
Avec Capgo
Solutions par type d'équipe
Trouvez la solution adaptée à vos besoins
Prêt pour des reviews plus rapides ?
Commencez dès aujourd'hui avec les channels aperçu PR
Commencez gratuitement. Aucune carte bancaire requise.