Skip to main content

Overview

Studio has 22 actions across 6 categories. The same picker opens for every page lifecycle event (On Screen Load, On Focus, On Blur, On Header Action) and for a component’s own touch events (On Tap, On Long Press, and the rest). Same search box, same six categories, same entries. This page lists what each action takes. For where actions are attached, see the page configuration docs.

How to read these tables

  • Control is what the parameter renders as in the panel: a text field, a dropdown, or a textarea.
  • Default or placeholder: a value in code is a real default, meaning the dropdown opens already showing it. A value in italics is a placeholder, which is grey hint text in an empty field. Leave the field alone and the action gets nothing, not the placeholder.
  • Required?: Studio marks no action parameter as required. There are no asterisks and no red validation, and every action can be left completely unconfigured. Where this column says effectively, that is an inference from the parameter’s purpose, not a label Studio shows.
  • Bind: most free text parameters carry Var and Bind controls on the label row, for pointing the parameter at a variable or at another component’s value instead of typing a literal.

Data

The API Call dropdown is gated on having an API call defined, not on having a backend connected. With one call defined and no backend connected, the dropdown lists that call. See Connect an API.

Interaction

Communication

Flow

Authentication

Exactly seven Authentication actions exist. All seven open and are fully readable with no backend connected, because the parameter forms are not gated behind a provider. Every one of them also carries On Success and On Error branches.

Which actions have On Success and On Error

Nine of the 22, and they are exactly the ones that talk to something outside the app. Each branch expands to its own + Add control that opens the same 22 action catalog, so an action chain can nest.

The Bind and Var affordances

Almost every free text parameter’s label row carries two small controls, Var and Bind. Bind opens a Search components… picker listing the page’s own bindable component nodes, by type and node id, each with a count and an expand chevron, such as Button button_1 (3) or Input input_1 (4). This is the same binding vocabulary a component’s own properties use. Three parameters have no Bind control: Run TypeScript’s Code (a textarea), Delay’s Duration (ms), and Set Variable’s Value, which has its own Static and Dynamic switch instead.

What a missing backend actually changes

Not the forms, the option lists. On a project with no backend connected, every Authentication action’s fields sit there ready to be bound to inputs that nothing will authenticate against. Toggle Overlay’s dropdown is empty until an overlay component exists on the page. Set Variable’s dropdown is empty until a variable is declared. The gating is data, not UI. So the presence of an Authentication action in a project says nothing about whether authentication is actually wired.

Troubleshooting

Style and tokens

Colour tokens, typography names, spacing and breakpoints.

Visibility rules

The four visibility and conditional style mechanisms.