How do timed transitions work in Adalo?
Use timed Adalo transitions for intentional loading or confirmation states while preserving a manual escape path, predictable navigation, and clear feedback.
Short answer
Use a timed transition only for a short, predictable state such as confirmation or onboarding, and ensure the destination does not depend on unfinished work.
Original walkthrough
Jul 3, 2021
The intended outcome
A short-lived screen that advances reliably and remains accessible.
Requirements
- Source and destination screens
- A reason not to use an immediate link
Step by step
Step 1: Keep the state short
Use a clear message and avoid hiding important input behind a timer.
Step 2: Configure the transition
Follow the legacy video as historical reference and confirm the current builder’s available screen actions before shipping.
Step 3: Provide an escape
For anything longer than a brief confirmation, allow the user to continue manually.
The underlying logic
Timed navigation is presentation, not a substitute for confirming that asynchronous work succeeded.
What changed?
- A current builder reproduction and terminology pass is still required.
Common failure modes
Move navigation after the relevant successful action rather than relying on elapsed time.
Testing checklist
0 of 3 checked on this device
Current limitations
- This legacy resource has not completed the current editorial and builder verification workflow.
Sources and status
This page was last reviewed on Aug 12, 2026. Its current status is Legacy video — current verification pending.
Verification owner: Pending editorial review. Next review: Oct 12, 2026.
The original Adalocado video is the primary source. A current official-source review has not yet been completed.
Changelog
Classified for improvement before search indexing.
Written and maintained by the Adalocado editorial team under the editorial and verification policy.
Did this solve your problem?
One-click check
We’ll handle the tech. You can exhale.
Bugs fixed. Updates shipped. Publishing handled.
$97/mo for your first 3 months.
Cancel anytime. That’s about 90% off the usual cost. 🤯
- Bug fixes and troubleshooting
- App updates and integrations
- Publishing and store releases
Bring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
