Skip to content
NewiPhone Duo, live in your browser. Try it →

Live devices Network access

Network access

The network your app gets on a VibeView device: internet access, IP allowlists for your backend, local servers, certificates, proxies and traffic inspection.

This page explains what network your app sees on a VibeView device, and how to connect the app to your own backend.

Internet access

Every iOS, Android, Apple TV, Android TV and Roku device has internet access. Your app reaches public servers, APIs and CDNs with nothing to configure.

Devices connect from VibeView’s network, not yours: a device can’t reach servers on your private network or your computer unless they are reachable from the public internet (see Your computer and local servers).

Apps that misuse the network

To keep the network fair for everyone, some apps are not allowed on any device, such as ones that sell the device’s network connection. See Restricted apps.

Backends that only allow known IP addresses

If your backend, CDN or firewall allows traffic only from known IP addresses, contact support@vibeview.io and we’ll send you the current addresses our devices connect from.

The addresses can change. If your allowlist starts refusing a device that used to connect, ask us for the current list.

Your computer and local servers

A device can’t reach localhost or other addresses on your computer.

The exception is Live development for your React Native app, on iPhone, iPad, Android phones and tablets, Apple TV and Android TV (not Roku). vibeview dev connects the device to the Metro bundler on your computer, so the app loads its JavaScript from it and hot-reloads as you edit. Only Metro is connected. Other services on your computer, such as a local API server, are not reachable from the device. Point the app at a server that is reachable on the public internet, such as a staging environment.

Certificates, proxies, inspection and network conditions

  • Certificates. Your servers need a certificate that devices trust out of the box, such as one from a public certificate authority. You can’t add your own root certificate to a device, so a self-signed certificate works only if your app itself trusts it.
  • Proxies. Routing a device’s traffic through an HTTP proxy you run is not supported.
  • Inspecting traffic. VibeView doesn’t capture your app’s network requests yet, so the Network tab on the Devices page shows none (see Network logs). To see what your app sends, log it from your app and read the app’s logs.
  • Network conditions. VibeView has no setting or test step that slows down, degrades or switches off a device’s network.

Questions about a network setup this page doesn’t cover? Contact support@vibeview.io.

Last updated 23 Oct 2026 Something wrong on this page? Tell us

Search the docs