Assume that you want to build a simple page with a button, and when the user presses the button another element of the page should appear -- and when you press the button again the element should disappear again.

As a developer I immediately think about this problem in terms of "state": The site has a state element that describes whether the thing is visible right now. The button then is responsible for modifying the current state (toggle between "visible" and "not visible"), and the element is responsible for actually showing itself when the state indicates that it should be visible.

Building this in Framer is possible., for example by creating a new set of overrides like this:

$${0}$$

The button gets the override `withToggleElementVisible`, and the element itself gets the override `withElementVisible`. I found it extremely easy to build this logic in Framer, and was ready to go on with my weekend... but there was a nagging feeling here: How could it be that I'm building something in a no-code and visual tool, and for the simplest interaction I ended up writing "hardcode react" code?

$${1}$$