Using templates in an app

Once a template screen exists, it behaves like any other feature.

Placing one

1. Open the app builder.
2. Find the screen in the feature sidebar under Your Templates.
3. Drag it onto a navigation bar.

It takes a title, an icon and role restrictions exactly like a plugin-backed feature. See Feature settings.

Shared editing

A placed template is a reference, not a copy. The block tree is stored with the template and read by every app that uses it.

Edit the template and every app changes, including apps you were not thinking about, at their next build. This is useful for anything genuinely shared — an about screen across three apps — and a hazard when you meant to change one.

If you want to change one app only, duplicate the screen first and place the duplicate.

Starter templates

The builder ships starter layouts, offered when you create an app. They are a reasonable structure to begin from rather than a commitment: everything they place can be moved, renamed or removed.

Starting from one is usually faster than starting from an empty canvas, because it shows you a working shape before you have opinions about your own.

Buttons that point at features

A Button block with the Feature action opens another placed feature. The target is stored on the app rather than the template, so:

• The same template in two apps can point at two different screens.
• If you remove the feature it points at, the button stops working. Nothing warns you, because from the template’s point of view nothing changed.

Check your template’s buttons after you rearrange navigation.

When it does not work

Symptom	Cause	Fix
A template is not in the sidebar	It has no saved screen yet	Add and save at least one screen
Editing broke another app	The template is shared by reference	Duplicate the screen and place the duplicate
A button stopped working	The feature it targeted was removed	Re-point it, or place the feature again
A new screen is refused	Free allows five screens across every project	See Plans and limits