--- schema_version: "1" id: 8f8b1809bd1998b7e631ada17b356ff2b5183e4ebc7c69fd267fcc1c2e5b0a85 title: Limitations for Mobile Publisher for Experience Cloud LWR Sites collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/branded_apps_lwr_gaps.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.branded_apps_lwr_gaps.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 103d69626441967b8852ce21f3806a55276375940928a28e2d52ac3b3dbb94c4 description: Experience Cloud sites are built on one of two frameworks—Lightning Web Runtime (LWR) or Aura. Each framework supports specific templates. Mobile Publisher for Experience Cloud supports all Aura templates and the Build Your Own (BYO) LWR template. Some limitations apply only to apps created from LWR sites. If your users need features that aren’t available with the BYO LWR template, use a site built with an Aura template instead. products: - Experiences - Mobile App - Cross Cloud release: "264" --- # Limitations for Mobile Publisher for Experience Cloud LWR Sites Experience Cloud sites are built on one of two frameworks—Lightning Web Runtime (LWR) or Aura. Each framework supports specific templates. Mobile Publisher for Experience Cloud supports all Aura templates and the Build Your Own (BYO) LWR template. Some limitations apply only to apps created from LWR sites. If your users need features that aren’t available with the BYO LWR template, use a site built with an Aura template instead. These Mobile Publisher limitations apply to apps created from [LWR sites and enhanced LWR sites](https://help.salesforce.com/s/articleView?id=experience.exp_cloud_basics_glossary.htm&type=5&language=en_US). ## Templates and Components - You can use only the Build Your Own (LWR) template. - A limited number of [standard Lightning components](https://help.salesforce.com/s/articleView?id=experience.networks_byo_lwr_components.htm&type=5&language=en_US) are available. To get more features and functionality, build [custom Lightning components](https://help.salesforce.com/s/articleView?id=experience.community_builder_custom_lightning_components.htm&type=5&language=en_US). - Sites hosted on Experience Delivery aren’t supported. ## Logout Flow The default logout flow, in which users are directed to your site login page at logout, isn’t available. And you can’t create a customized logout experience. Instead, manually add a Logout link in your site header that points to /secur/logout.jsp. The code in logout.jsp redirects to the Salesforce login page (login.salesforce.com). ## Authentication Multi-factor authentication workflows aren’t supported in apps created with Mobile Publisher for the LWR platform. ## Navigation In Experience Builder, the features in the Additional Navigation Options section (**Settings** | **Mobile Publisher** | **Navigation**) are available only for Aura sites on the Customer Account Portal, Partner Central, Customer Service, and Help Center templates. The additional navigation options aren’t supported in apps created from LWR sites. ## Notifications - Mobile Publisher for apps created from LWR sites supports notifications and routing notifications to the appropriate targets. However, the standard bell component that shows the count of all unread notifications isn’t available for LWR sites. As a result, the standard in-app bell icon component for notifications isn’t available on apps created from LWR sites. To include a notifications bell icon in your app, build a custom Lightning web component that uses the [Notifications API](https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/connect_resources_notifications_list.htm). A custom component that uses the Notifications API also marks notifications as read, which enables an app’s badge to show the correct count of unread notifications. When used with a Mobile Publisher app, the Notifications API supports both standard and custom notification types. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-branded_apps_exp_cloud-264-0-0-production-enus/cf85363c-215e-4784-bb6a-c5c83c4e7140/images/icon_tip.png) Tip For an example component that uses the Notifications API, see [Notification Bell for Experience Cloud (LWR)](https://appexchange.salesforce.com/appxListingDetail?listingId=fd51a7d1-d4cb-486f-997e-b6fb87cc8e25&tab=d) in AppExchange. To view the open-source code for the example component, see [salesforce-experiencecloud/notificationbell](https://github.com/salesforce-experiencecloud/notificationbell) in GitHub. - Custom Lightning web components and the Aura notifications component within a Mobile Publisher app don’t support polling. Without polling, the notifications component shows new notifications only when the app is refreshed. ## Other Limitations - Messaging for In-App and Web isn’t supported. - Mobile Publisher for Experience Cloud sites doesn’t support iframe integration. If your app includes the iframe element, your app users can experience functionality issues. #### See Also - [Custom Login Flow Considerations](https://help.salesforce.com/s/articleView?id=xcloud.custom_login_flow.htm&release=264.0.0&type=5 "A login flow directs users through a login process before they access your Mobile Publisher for Experience Cloud app. After Salesforce authenticates a user, the login flow directs the user through a process, such as enforcing strong authentication or collecting user information. When users complete the login flow successfully, they’re redirected to their Mobile Publisher for Experience Cloud site. If unsuccessful, the flow can log out users immediately.")