# Page Parameters for Better State Management

**URL:** <https://forum.adalo.com/t/page-parameters-for-better-state-management/66221>\
**Category:** Feature Requests\
**Tags:** open, external-integration\
**Created:** [April 9, 2026, 7:29am UTC](https://forum.adalo.com/t/page-parameters-for-better-state-management/66221 "2026-04-09T07:29:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeorge](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/jeorge/32/40256_2.png) [@Jeorge](https://forum.adalo.com/u/Jeorge)\
**Post date:** [April 9, 2026, 7:29am UTC](https://forum.adalo.com/t/page-parameters-for-better-state-management/66221/1 "2026-04-09T07:29:31Z")

</div>

Hey everyone 👋

While working on a recent flow, I realized how much easier things would be if Adalo supported **page-level parameters**.

### The Idea

Introduce simple **page parameters** that can store temporary values and be accessed across components within a screen.

### MVP Scope

For a start, this could be very simple:

- Support basic types: **text, number, date**

- Ability to:

### Why This Matters

Right now, we rely on workarounds like hidden inputs to manage temporary UI states (e.g. showing success messages, toggling views). While it works, it’s not very clean or scalable.

Page parameters would:

- Simplify UI state handling

- Reduce reliance on hidden components

- Make apps easier to structure and maintain

### Nice-to-Have (Future)

If possible (even if later):

- Ability to **pass/set parameters when navigating between screens**

This would open up much cleaner patterns for handling transitions and temporary data between screens.

Would love to hear thoughts from the team and others on this 🙌