Skip to content

Add FAQ to clarify variable type limitations in App State #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 30, 2025
Merged

Add FAQ to clarify variable type limitations in App State #401

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cc3208d
Add FAQ to clarify variable type limitations in App State
pinkeshmars Jun 20, 2025
88e7ba8
Merge branch 'main' into fix/faq-app-state-variable-type
PoojaB26 Jun 28, 2025
5772dba
Merge branch 'main' into fix/faq-app-state-variable-type
PoojaB26 Jun 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/resources/data-representation/app-state.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,3 +114,17 @@ Here's a quick guide to updating the app state variable. We need to add an actio
</iframe>
</div>

## FAQs

<details>
<summary>
Why are some variable types not available in App State?
</summary>
<p>
Certain variable types, e.g., **Firestore Documents** and **Supabase Row**, can be used in Page State or Component State, but not in App State. This is because App State variables are designed to be global, meaning they stay in memory throughout the app. When App State variables are marked as persisted, the variable’s value is saved to the device’s local storage.

Storing large or complex data types like documents in App State could lead to **performance or size issues**, especially on lower-end devices. For this reason, FlutterFlow limits App State to lightweight types, while Page/Component State allows for more flexibility since their scope is smaller and temporary.

If you need to work with such data types, it's recommended to store them in Page or Component state instead.
</p>
</details>