# Web Container {% hint style="info" %} **Version compatibility** * Web support is compatible with runtime versions **4.72.0** and later. * Only the latest stable version of Google Chrome on Windows, Linux or MacOS is currently supported. {% endhint %} ### Feature Support Some features have not been implemented yet, and some features cannot be supported in a web browser. | Feature | Status | Notes | | ------------------------------------------------------------------------------------------------------------------------------ | ------------------- | ------------------------------------------------------------------------ | | SSO | Supported | | | Enrollment via link | Supported | | | Deep linking | Planned | | | [Select photo from gallery](https://docs.journeyapps.com/reference/build/ui-components/all-ui-components/capture-photo#source) | Supported | | | Customize login screen | Partially supported | The [favicon can be customized](#custom-web-container-favicon). | | Custom domain names | Supported | | | [GPS](https://docs.journeyapps.com/reference/app-features/gps-capturing) | Limited support | Based on what the browser is able to provide. | | [Barcode Scanning](https://docs.journeyapps.com/reference/build/integration/barcode-scanning) | Not supported yet | | | [Push Notifications](https://docs.journeyapps.com/reference/app-features/push-notifications) | Not supported yet | | | Offline support | Not supported yet | | | Other browsers | Not supported yet | Support for Safari, Firefox and the new Edge may be added in the future. | | Database Encryption | Not supported | Not feasible on web. | | [Serial Port](https://docs.journeyapps.com/reference/build/js-ts-apis/serialport) | Not supported | Not supported yet. | | [BLE](https://docs.journeyapps.com/reference/build/js-ts-apis/bluetooth-low-energy-beta) | Supported | | | [NFC](https://docs.journeyapps.com/reference/build/js-ts-apis/nfc) | Not supported | Not supported yet. | | [TCP](https://docs.journeyapps.com/reference/build/js-ts-apis/tcp-sockets) | Not supported | | ### FAQ #### Can the same application be opened in multiple tabs? Yes. #### Where will users access the app? By default you will get a domain name such as `your-app.onjourneyapps.com`. For custom domain names: 1. Configure the DNS record for the domain as `CNAME web-container-router.journeyapps.com`. 2. Contact [JourneyApps Support](mailto:support@journeyapps.com) to configure the web container with the custom domain. A certificate will be provisioned automatically for the domain using Let's Encrypt. ### Getting Access Contact [JourneyApps Support](mailto:support@journeyapps.com) to request web access for an app. If you'd like to specify the [web container's favicon](#customize-the-web-container-favicon), please include a 64x64 px .png file of the icon. ### Custom Web Container Favicon {% hint style="info" %} **Version compatibility** Support for customizing the favicon of the Web container was added in version **4.86.1** of the JourneyApps Runtime and version **22.9.4** of the JourneyApps Container. {% endhint %} By default, the JourneyApps logo is displayed as the web container favicon:
This icon can be customized, by providing a 64x64 px png file of the icon when [requesting a Web Container](#getting-access). Once a user enrolls in an app in this container, the JourneyApps Runtime dictates which favicon is being displayed:
For apps using JourneyApps Runtime version 4.86.1 (or greater), the Runtime will load the app-level favicon as follows: 1. If no custom container- or app-level favicon is specified, the standard JourneyApps logo will be displayed as per the screenshots above. 2. If only a [container favicon is specified](#getting-access), that favicon will be displayed. 3. If an app-level favicon is specified (see the [section below](#configure-app-level-favicon)), that icon will be displayed. All apps running with a Runtime version lower than 4.86.1 will display the standard JourneyApps logo as the favicon. #### Configure app-level favicon You can specify an app-level favicon (and thereby override the container-level favicon) using OXIDE. Step 1:\ Upload the icon into OXIDE’s assets for your app, example:\ ![](https://2865107717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9TCHLR67eLHBOjPvHhud%2Fuploads%2FR13cq0O8aRVCelecPAaG%2Fimage.png?alt=media\&token=f78cc35a-1294-442d-bfdd-94edcf37ff61) Step 2:\ Open up the `config.json` file in OXIDE, and add a line the references the icon as follows: 
    ...
    "runtime_version": "4.86.1",
    "app_icon": "icons/check_one_icon.png",
    ...
Step 3:\ Deploy!
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.journeyapps.com/reference/technical/supported-platforms/web-container.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.