Custom State

When you’re building an app in a no-code platform, you often need a way to store temporary values. For example, maybe you want to remember which tab a user clicked, which filter they selected, or whether a popup is visible. Saving these small details in the database isn’t efficient. Instead, you use something called a custom state.

A custom state is a flexible, temporary memory that belongs to an element, page, or app. Unlike database values, custom states are not permanent—they reset when the page is refreshed. They’re a key feature in platforms like Bubble and make apps interactive, fast, and user-friendly.

In this guide, I’ll explain what custom states are, how they work, examples of how to use them, and why they’re so useful in no-code app development.

What is a Custom State?

A custom state is a temporary value you define for an element, page, or app. It lets you store data only while the app is running. Once the user leaves or reloads the page, the value disappears.

Custom states are useful for things like:

• Showing or hiding popups
• Remembering which tab is active
• Storing filters or search terms
• Keeping count of clicks or steps in a process
• Holding temporary data before it’s saved to a database

In short, a custom state is like short-term memory for your app.

How Custom States Work in No-code Platforms

Custom states usually follow a simple structure:

1. Name – The label for your state (e.g., “PopupVisible”).
2. Type – The kind of value it holds (yes/no, number, text, list).
3. Default value – The starting point before the state changes.
4. Change trigger – The event that updates the state (like a button click).

Example in Bubble:

• Create a custom state on a page: “TabSelected (text).”
• User clicks “Reviews” tab → Custom state changes to “Reviews.”
• Workflow checks state → Show content based on state value.

This allows you to control what users see or do instantly, without hitting the database.

Benefits of Using Custom States

Custom states give apps speed and flexibility.

Key benefits include:

• Instant response – Update app behavior without reloading.
• Faster performance – No need to query the database for small changes.
• Flexibility – Store anything from a single value to a list.
• Cleaner workflows – Keep temporary values separate from permanent data.
• Better user experience – Make apps feel smooth and interactive.

They’re especially helpful for UI/UX control, like switching tabs or showing dynamic filters.

Examples of Custom States in Action

Here are some practical ways custom states are used in no-code apps:

• E-commerce app – Store selected filter (e.g., “Shoes under $50”) as a state.
• Booking app – Track which date or slot the user has clicked.
• Social app – Toggle like/unlike button using a yes/no state.
• Dashboards – Switch between charts based on tab state.
• Multi-step forms – Store progress (Step 1, Step 2) until submission.

These use cases make apps dynamic without constant database updates.

Custom State vs Database

It’s important to know when to use a custom state and when to use a database.

• Custom state – Temporary memory, clears when page reloads. Best for UI conditions, filters, or step tracking.
• Database – Permanent memory, saves even after reload. Best for user profiles, orders, or records you need to keep.

Use custom states for speed and flexibility. Use databases for long-term storage.

Custom States in Popular No-code Platforms

Different platforms handle custom states in their own way:

• Bubble – Custom states can be attached to any element or page. Very flexible.
• Glide – Uses user-specific columns that act like custom states.
• FlutterFlow – Stateful widgets track temporary conditions.
• Adalo – Conditional visibility and variables mimic custom state behavior.
• Webflow – Achieved through interactions and temporary conditions.

Bubble is the most famous for custom states, but the concept exists in most platforms.

How to Use Custom States Effectively

To get the best from custom states, follow these tips:

• Name them clearly – Example: “MenuOpen” instead of “State1.”
• Keep them simple – Don’t overload with unnecessary values.
• Combine with workflows – Use states to trigger actions instantly.
• Reset when needed – Clear states after use to avoid errors.
• Use database wisely – Only store permanent data, not temporary states.

This ensures your app stays organized, fast, and easy to maintain.

Conclusion

A custom state in no-code is a temporary value you define to control app behavior without saving it permanently. It’s perfect for UI interactions, filters, and short-term conditions.

Whether you’re building in Bubble, Glide, FlutterFlow, or Adalo, mastering custom states will make your apps smoother, faster, and more dynamic. They’re the secret ingredient behind great user experiences in no-code development.