PR-Vorschau

Testen Sie jeden PR auf echten Geräten

Vergessen Sie TestFlight-Wartezeiten und Beta-Channel-Chaos. Erstellen Sie einen Vorschau-Channel für jeden Pull Request und lassen Sie Ihr Team auf echten Geräten testen - in Sekunden statt Stunden.

Kein TestFlight nötig
Sofortiges Testen
Auto-Bereinigung

Das Problem

Das TestFlight-Problem

Traditioneller Workflow

1

Developer Opens PR

Code is ready for review. But before anyone can test it, you need to build and upload to TestFlight.

2

Build and Upload

Build the app locally or in CI. Archive it. Upload to App Store Connect. Wait for processing. 15-30 minutes minimum.

3

Distribute to Testers

Add testers if they're not already in TestFlight. Send invites. Wait for them to accept. Explain how to install.

4

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.

Stunden verschwendet für jeden PR-Review

Wahre Kosten pro PR

15-30 Minuten

TestFlight-Verarbeitung

Durchschnittliche Wartezeit für TestFlight-Verarbeitung

67%

QA blockiert

Zeit, die QA auf jeden Build wartet

$340/PR

Die versteckten Kosten des Wartens auf Reviews

Verlorene Produktivität durch Warten

Die Lösung

PR-Vorschau-Channels

Automatische Vorschau-Channels für jeden Pull Request

1

Developer Opens PR

CI automatically builds the app and creates a Capgo channel named after the PR number.

Automatic

2

Bundle Uploads

The built bundle uploads to Capgo in the background. No processing delay.

< 30 seconds

3

Tester Switches Channel

Tester opens the app, switches to the PR channel, and gets the build immediately.

< 10 seconds

4

Test and Approve

QA tests on real device. Dev pushes fixes. Tester immediately gets updates. No reinstall needed.

Instant iteration

.github/workflows/pr-preview.yml
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 }}`'
            })

Einrichtungszeit

Wie Tester zu Ihrem PR-Build wechseln

Schüttelmenü (kein Code)

Aktivieren Sie die integrierte Schüttelgeste. Tester schütteln ihr Gerät, um ein Menü mit allen verfügbaren Kanälen zu öffnen.

// capacitor.config.ts
CapacitorUpdater: {
  shakeMenu: true // Enable for testing
}

In-App Umschalter

Erstellen Sie eine benutzerdefinierte Oberfläche zum Wechseln von Kanälen. Perfekt für einen Entwicklereinstellungsbildschirm in Ihrer App.

// Switch channel from your app
import { CapacitorUpdater } from '@capgo/capacitor-updater'

await CapacitorUpdater.setChannel({
  channel: 'pr-123'
})

Praxisbeispiel

So funktioniert es

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% schnellere PR-Reviews

Time to first QA feedback < 5 min
PRs merged per sprint +156%
QA wait time -87%
Time to merge 0.6 days

"PR-Vorschau-Channels haben unsere Review-Zeit von Stunden auf Minuten reduziert. Game changer für unser Team."

— Sarah K., Lead Developer

Entwickelt für Teams

Jede Rolle profitiert von sofortigen Vorschauen

QA-Ingenieure

  • Test any PR on your device in seconds
  • Switch between PRs instantly to compare behavior
  • No more confusion about which build you're running

Projektmanager

  • Review features before they ship
  • No technical setup - just tap a link
  • Provide feedback directly on the PR

Entwickler

  • Get QA feedback before your context switches
  • Push fixes and testers get them instantly
  • No more 'waiting for build' blockers

Der Unterschied

Traditionell

Mit Capgo

Build-Zeit
15-30 min
<1 min
Zwischen Builds wechseln
5+ min reinstall
10 seconds
Einrichtung
Stunden der TestFlight-Konfiguration
5 Minuten CI/CD-Integration
Bereinigung
Manuelle Build-Löschung
Automatisch beim PR-Merge

Bereit für schnellere Reviews?

Beginnen Sie noch heute mit PR-Vorschau-Channels

Kostenlos starten. Keine Kreditkarte erforderlich.