Vista previa de PR

Prueba cada PR en dispositivos reales

Olvida las esperas de TestFlight y el caos de canales beta. Crea un canal de vista previa para cada Pull Request y deja que tu equipo pruebe en dispositivos reales - en segundos.

Sin TestFlight
Pruebas instantáneas
Limpieza automática

El problema

El problema de TestFlight

Flujo tradicional

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.

Horas perdidas en cada revisión de PR

Coste real por PR

15-30 minutos

Procesamiento TestFlight

Tiempo de espera promedio para TestFlight

67%

QA bloqueado

Tiempo que QA espera por cada build

$340/PR

Los costes ocultos de esperar

Productividad perdida esperando

La solución

Canales de vista previa de PR

Canales de vista previa automáticos para cada 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 }}`'
            })

Tiempo de configuración

Cómo los testers cambian a tu build de PR

Menú de agitar (sin código)

Habilita el gesto de agitar integrado. Los testers agitan su dispositivo para abrir un menú que muestra todos los canales disponibles.

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

Selector en la app

Construye una UI personalizada para cambiar canales. Perfecto para una pantalla de configuración de desarrollo en tu app.

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

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

Caso real

Cómo funciona

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% revisiones de PR más rápidas

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

"Los canales de vista previa de PR redujeron nuestro tiempo de revisión de horas a minutos. Game changer."

— Sara K., Lead Developer

Diseñado para equipos

Cada rol se beneficia de vistas previas instantáneas

Ingenieros 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

Project Managers

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

Desarrolladores

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

La diferencia

Tradicional

Con Capgo

Tiempo de build
15-30 min
<1 min
Cambiar entre builds
5+ min reinstall
10 seconds
Configuración
Horas de configuración TestFlight
5 min de integración CI/CD
Limpieza
Eliminación manual de builds
Automático al merge del PR

¿Listo para revisiones más rápidas?

Comienza hoy con canales de vista previa de PR

Comienza gratis. Sin tarjeta de crédito.