Toggle is a simple concept, on the surface. But, as with most things in UX, it’s important to think about how and when it should be used.

Toggles are a great way to manage the state of something, whether that’s content or a view. They’re best when used to allow people to toggle between two opposing values that affect the status of an item—rather than letting them select from a list. Toggles can be a useful complement to other input elements such as sliders and checkboxes.

Available to Grandmaster subscription tier and above.

Visibility toggles allow you to make areas of your articles private or public at a moment’s notice without having to edit the article itself.

This is a space for you to ask basic questions as you get started with Evolve, or more complex best practice questions for more experienced designers. We will do our best to respond within 24 hours.

Note: In Ionic 7.0, we introduced a simplified syntax for toggle that reduces boilerplate and resolves accessibility issues. We recommend migrating to this new syntax as soon as possible.

Name your toggles carefully. This helps developers across teams understand what each toggle does, and gives them context when debugging or reading error messages.

Oftentimes, feature flags are stored in static files that must be modified manually. This can be cumbersome when managing a large number of toggles, and it makes it difficult to test or compare changes. To address these problems, many organizations move their toggle configuration into some type of centralized store, such as an existing application database.