About the Connect web app
The Connect web app is automatically available as part of all Pexip Infinity deployments. It provides a WebRTC interface to Pexip Infinity conferencing services.
The web app is supported in the following browsers. We strongly recommend using the latest publicly-released version (i.e. "stable version" or "supported release") of a browser, and while we aim to support all recent versions of the browser, support is guaranteed only against the latest versions available at the time of release, as follows:
- Google Chrome version 126 and later (64-bit only) on Windows, Linux, macOS, iOS*, and Android*
- Mozilla Firefox version 128 and later on Windows, Linux, macOS, and iOS*
- Microsoft Edge version 126 and later (64-bit only) on Windows and iOS*
- Apple Safari version 15.4 and later on macOS and iOS*
* For the best experience on mobile devices, we recommend using the Connect mobile apps.
Connect app users can share their screen, images and PDFs from any browser.
Connect web app versions
There are two versions of the Connect web app currently available:
- Connect Webapp3: the current version, released with Pexip Infinity version v30. We are constantly adding new features and functionality and it is our recommended version.
- Connect Webapp2: the previous version, released with Pexip Infinity version v18. This version is no longer under active development.
Both versions are available from your Pexip Infinity deployment. For a comparison of the two versions, and information on how to configure which version you want to offer web app users by default, see Connect web app versions and differences.
Support for first-time and infrequent users
Connect Webapp3 offers two levels of assistance for participants prior to joining a meeting.
The default is the "express" flow, designed for frequent users who are familiar with setting up and using Connect Webapp3 and who want to join a meeting quickly and simply. When using this flow, the participant's name will be remembered, so all they need to do is enter the meeting name, check that their devices are working and enabled or disabled as expected, and join the meeting.
The second "step-by-step" flow is designed for participants who might be using Connect Webapp3 for the first time or infrequently, and who might require some guidance. This flow takes users through the process of entering their name and then setting up their camera, speaker, and microphone, allowing them to select each device and test that it is working before moving on to the next. This flow also provides users who can't see, speak or hear with the opportunity to enable further support.
The same meeting can be joined by participants using either flow. To enable the "step-by-step" flow for a participant, include role=guest within the URL that you provide them with to join the meeting. All other participants who join the meeting using a URL that does not include this parameter will join using the express flow. For more information, see Links to a specific meeting with additional parameters included.
Language support
Connect Webapp3 natively supports over 20 of the most popular languages. If
Administrators can add additional languages using branding and customization.
Administrators can restrict which languages are supported via the availableLanguages setting in the manifest file. When this option is specified, if a user's browser is set to use a language not included in the availableLanguages list, the default en.json is used. Additionally, the languages available to users from within the menu is restricted to only those specified in the availableLanguages list. This option can be used if, for example, administrators edit their language files to use specific terminology and want to limit the number of language files they need to maintain.
Connect Webapp3 currently supports the following languages:
| Code | Native name | English name |
|---|---|---|
| en | English | English |
| cs | Česky | Czech |
| cy | Cymraeg | Welsh |
| da | Dansk | Danish |
| de | Deutsch | German |
| es-ES | Español | Spanish (Spain) |
| es-US | Español de Ustados Unidos | Spanish (Americas) |
| fi | Suomi | Finnish |
| fr-CA | Français (Canadien) | French (Canada) |
| fr-FR | Français | French (France) |
| ga | Gaeilge | Irish |
| id | Bahasa Indonesia | Indonesian |
| it | Italiano | Italian |
| ja | 日本語 | Japanese |
| ko | 한국어 | Korean |
| nb | Norsk (bokmål) | Norwegian (Bokmål) |
| nl | Nederlands | Dutch |
| pl | Polski | Polish |
| pt-BR | Português | Portuguese (Brazil) |
| sv | Svenska | Swedish |
| th | ภาษาไทย | Thai |
| vi | Tiếng Việt | Vietnamese |
| zh-Hans | 简体中文 | Chinese (Simplified) |
| zh-Hant | 繁體中文 | Chinese (Traditional) |
Accessing a conference or making a call
Connect Webapp3
To access a conference or make a call using Connect Webapp3, users enter into their browser's address bar the IP address or domain name of their nearest Conferencing Node or reverse proxy.
System administrators and conference organizers can also provide a preconfigured link to a meeting, with one or more options (such as the meeting name) already configured.
Connect Webapp3 offers two different joining flows:
-
Express flow: by default, users are simply asked to enter the Meeting ID (if not already included in the URL), which is the alias of the conference or person they want to call. They then get the opportunity to check their setup (camera, microphone and speakers) before selecting .
This flow is aimed at users who are familiar with the web app and want to join a meeting quickly.
- Infrequent/guest user: for occasional or less experienced users who might require assistance with selecting and checking their camera, microphone and speakers, you can include &role=guest in the URL you give them to join the meeting. This offers them an alternative join flow that takes them through the setup of their camera, microphone and speakers before they are able to the meeting. For more information, see Creating preconfigured links to launch conferences via Connect apps.
Connect Webapp2
To access a conference or make a call using Connect Webapp2, users enter into their browser's address bar the IP address or domain name of their nearest Conferencing Node (or reverse proxy if, for example, it is being used to host a customized version of the web app), followed by /webapp/home (for example, confnode.pexample.com/webapp/home). Users are then presented with the home screen, from where they can check their setup and then select to enter the alias of the conference or person they want to call.
System administrators and conference organizers can also provide a preconfigured link to a meeting, with one or more options (such as the meeting name) already configured.
Enabling access for external users
If your Pexip Infinity deployment is located inside a private network and you want to allow Connect app users who are located outside your network to connect to your deployment, see Using the Connect app from outside your network.
Hardware requirements
The performance of the Connect web app typically depends on a combination of factors including
We recommend that your client device has a minimum of 4 GB of RAM.
In addition, note that use of background effects (blur and replacement) incur a significant local processing overhead which could affect the performance of your device.