How To Use Web Fallbacks in MemberPress App

Web Fallbacks display WordPress pages and custom post types within the mobile application. These pages load responsively with site headers and footers automatically hidden. This document explains how to configure Web Fallbacks and understand their use cases compared to native App Pages.

Understanding Web Fallbacks

Web Fallbacks embed existing WordPress content within the app interface. Pages display with the app's native header while website headers and footers remain hidden. Web Fallbacks support page builders and existing content without requiring custom development.

Comparing Web Fallbacks and App Pages

Web Fallbacks and App Pages serve different purposes with distinct advantages.

Web Fallback Characteristics

Existing content integration allows WordPress pages to display in the app. Content created with page builders or the standard WordPress editor works without modification.

Internet connectivity is required for Web Fallback loading. Pages fetch content from the server each time members access them.

Site speed-dependent performance varies with hosting and page optimization. Complex pages may load more slowly than native alternatives.

Development efficiency eliminates the need for custom app development. Existing web pages integrate directly into app navigation.

App Page Characteristics

Native screen experience provides smooth navigation with instant loading. App Pages built with App Blocks load from local cache.

Offline availability allows content access without an internet connection. Cached content remains accessible during offline periods.

Performance optimization delivers faster loading than web content. Native rendering eliminates external server requests.

Custom work is required to create an App Page using App Blocks. Pages must be built specifically for app display.

Accessing Menu Configuration

Web Fallbacks are added through menu configuration interfaces.

1. Navegue até Dashboard > MP App > Menus.
2. Select either Tab Bar Menu ou More Screen Menu.

3. Clique no botão Salvar menu if previous changes require saving.

Adding Web Fallback Pages to Navigation

Web Fallback pages are added as menu items linking to WordPress content.

1. Navegue até Dashboard > MP App > Menus.
   
2. Select the menu requiring the Web Fallback addition.
   
3. Locate available pages under WordPress Pages ou MemberPress App sections.

4. Find the page to display as Web Fallback.

5. Clique em Adicionar ao menu next to the page name.
   
6. Drag the menu item to the desired navigation position.
   
7. Clique no botão Salvar menu to finalize changes.

Common Web Fallback uses include shop pages, resource libraries, and custom post type archives.

Previewing Web Fallback Content

Web Fallback verification ensures proper display within the app interface.

1. Open the MemberPress App on a mobile device.
2. Navigate to the menu containing the Web Fallback item.
3. Tap the Web Fallback menu item to open the page.
4. Verify the page loads without the site header and footer.
5. Confirm the app's native header displays above the content.
6. Tap content links to navigate within the Web Fallback.
7. Use the app's back arrow to return to previous screens.

Web Fallback pages maintain responsive design and mobile optimization from the original WordPress page.

Understanding Deep Linking Behavior

Deep linking connects Web Fallback content to native app screens when applicable.

Native screen detection occurs when Web Fallback links match app screen URLs. The app opens the appropriate native screen instead of loading web content.

Seamless transitions provide smooth navigation between web and native content. Members experience a consistent interface regardless of the content source.

Automatic URL recognition identifies supported native screens from link destinations. No additional configuration is required for deep link functionality.

Comparing Native Screens and Web Fallbacks

Recurso	Web Fallbacks	Native App Pages
Setup Complexity	Easy – Use existing pages	Advanced – Requires REST API + coding
Performance	Slower, internet-dependent	Fast and responsive
Offline Availability	Not supported	Fully supported
Visual Integration	Matches app layout, not perfect	Fully integrated
Construtores de páginas	Supported (Elementor, Gutenberg)	Not applicable