Moving between screens

Navigate to screen with a transition, Back — and the difference between “over” and “replace”.

A button, its Logic tab, and the navigation already wired up.
A button, its Logic tab, and the navigation already wired up.

Select a button or a card and pick a screen in On tap, the first row of the Content tab on the right. That is enough for an ordinary transition. “Configure in detail” opens the rest.

  • How to open. “Over (with back)” stacks the screen, and Back returns where you came from. “Replace (like a tab)” does not grow the stack — that is how bottom-menu items behave.
  • Transition — the animation: slide left or right, fade, push, or bottom-up. Bottom-up reads well for sheet-like screens such as a cart or filters.

What a visitor sees after a reload and from a link. After reloading the page they stay on the start screen or bottom-menu tab they were on. A detail screen is not restored: the choice it relied on is gone, and it would open empty. Someone arriving from a link to a screen gets the start screen underneath it, so Back leads there; a bottom-menu tab opens without Back, since the rest of the app is already in the menu. In an app that works as a website, Android’s system back walks through the screens and leaves the page only from the start screen.

Read next