State allows us to create interactive apps that can respond to user input. It defines the variables that can change over time, and the functions that can modify them.

You can define state by creating a class that inherits from rx.State:

A state class is made up of two parts: vars and event handlers.

Vars are variables in your app that can change over time.

Event handlers are functions that modify these vars in response to events.

These are the main concepts to understand how state works in Reflex:

Here is a example of how to use state within a Reflex app. Click the text to change its color.

The base vars are colors and index. They are the only vars in the app that may be directly modified within event handlers.

There is a single computed var, color, that is a function of the base vars. It will be computed automatically whenever the base vars change.

The heading component links its on_click event to the ExampleState.next_color event handler, which increments the color index.

Each user who opens your app has a unique ID and their own copy of the state. This means that each user can interact with the app and modify the state independently of other users.

Because Reflex internally creates a new instance of the state for each user, your code should never directly initialize a state class.

All user state is stored on the server, and all event handlers are executed on the server. Reflex uses websockets to send events to the server, and to send state updates back to the client.

Similar to backend vars, any method defined in a State class that begins with an underscore _ is considered a helper method. Such methods are not usable as event triggers, but may be called from other event handler methods within the state.

Functionality that should only be available on the backend, such as an authenticated action, should use helper methods to ensure it is not accidentally or maliciously triggered by the client.