For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Build a screen out of native elements instead of loading a web page.

A native screen is built from elements you arrange yourself — a title, a banner, a row of products, a countdown — rather than loading a page from your website.

Because nothing has to be fetched and rendered as a web page, a native screen appears the moment a customer taps its tab. It scrolls like an app, not like a website in a frame.

Native screens are a Premium feature. You add one from Screens → Add New Screen by choosing Native screen as the screen type — see Add New Screen.

When to use one

Use a native screen when the page is yours to design rather than yours to mirror — a home screen, a promotions page, a landing page for a campaign.

Keep a web screen when the content already exists on your site and changes often. A product catalogue of thousands of items belongs on the web screen that already renders it; recreating it element by element means maintaining it twice.

A good app usually has both: a native home screen that opens instantly, and web screens for the catalogue, cart and checkout.

How it is built

Open a native screen and you get three panels: the element list on the left, a live phone preview in the middle, and the selected element's settings on the right.

Click Add Element, pick a type, and it appears in the preview straight away. Drag elements in the list to reorder them.

Each element has up to two tabs:

  • Content — the words, images and links in it.

  • Settings — how it looks: text style, colours, spacing, margins, and who sees it.

Elements

Visibility

Every element can be shown or hidden by Platform (All, Android, iOS), Device (All, Mobile, Tablet & iPad) and User (All, Logged-in users, Non logged-in users).

This is how one screen serves two audiences: a Welcome back title for signed-in customers and a Create an account banner for everyone else, both on the same screen, each seen by only one group.

Saving

Changes are held as a draft until you click Save as draft, and reach customers when you publish a build.

Last updated