Home

Opens a URL of your choosing in a webview, as the app’s home.

Before you start

Plugin	None
Endpoint group	None
Plan	Every plan

Add it to your app

1. Drag Home onto a navigation bar, usually the first bottom-nav slot.
2. Set the URL.
3. Set a Title.

Settings

Setting	What it does	Default
URL	The address to open	Empty
Title, Description	The tab label and heading	Empty
Restrictions	Which roles see the tab	Everyone

Think twice before making this your home

A tab that loads your website is the fastest way to fill a bottom-nav slot, and the weakest screen in the app. It is slower than a native screen, it shows your site’s header and footer inside an app that already has navigation, and it does not follow your app’s theme.

It also carries real store risk. Apple rejects apps that are largely wrappers around a website under guideline 4.2, and an app whose home tab is a webview is the shape reviewers look for. See iOS builds.

Prefer a native screen for the home tab. A News Feed, a Posts screen, a Directory, or a template screen you compose yourself all make better first screens.

Use Home when you genuinely need a web page that cannot be rendered natively — a dashboard from another plugin, for instance.

Members stay signed in

The webview carries the member’s session, so a page behind a login shows them signed in rather than asking again.

When it does not work

Symptom	Cause	Fix
The tab is blank	The URL is empty or unreachable	Set it, and open it in a browser to check
It asks members to sign in again	The session did not carry	Confirm your site serves over HTTPS
Site header and footer appear	It is a web page, not a native screen	Use a native feature instead
It ignores dark mode	Webviews follow your website, not the app	Use a native feature
Content is cut off sideways	The page is not responsive	Fix it on your site