PRODUCTIVITY
My Swisscom
Account app where support, plan, and billing changes should ship quietly.
Set & Forget
Install the native app once through your private store or MDM. After that, ship web fixes through Capgo, track who received them, and keep offline devices on the last good bundle.
Channel map
Store and enterprise package releases are slow to coordinate and hard to verify across every device. Capgo gives you an instant release path for the web layer, with channels, device logs, staged rollout, and rollback built in.
Distribute the signed iOS or Android app through MDM, an enterprise app store, or your internal device provisioning flow.
Use a default channel for production, then split by site, country, team, or hardware generation when needed.
Build, test, and upload the Capacitor web bundle to Capgo. Native code changes still go through your normal enterprise packaging process.
Devices fetch updates during planned connectivity windows and keep the last good bundle locally for offline use.
Use channels, device logs, staged rollout, and rollback so local teams are not asked to debug production installs.
Use Capgo as the release layer for web assets, not as a replacement for your native distribution process. Native binaries still move through your enterprise packaging flow.
Use Capgo as the release layer for web assets, not as a replacement for your native distribution process. Native binaries still move through your enterprise packaging flow.
# Build and publish the web layer
npx @capgo/cli@latest bundle upload --channel site-eu
# Promote after the first site validates it
npx @capgo/cli@latest channel set production com.enterprise.app --latest const config = {
plugins: {
CapacitorUpdater: {
defaultChannel: 'production',
autoUpdate: true,
},
},
} Apps built with Capacitor
Telecom and support apps have billing, plan, support, and device workflows that must stay current without asking users to install a new binary for every small improvement.
PRODUCTIVITY
Account app where support, plan, and billing changes should ship quietly.
TOOLS
Carrier self-service app where users should not manage every minor update.
Tools
Support app where diagnostic and help flows need maintenance without release overhead.
Map channels, rollout rules, and tracking around your real operating model.