You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is the UI to create a new segment:
To proceed, users must choose between "Add AND Condition" or "Add AND NOT Condition". I don't have data to back this up, but I would guess the vast majority of users will start by creating an AND condition. For unfamiliar users and demos, this masks what segments are for - if we showed the "trait" "condition" "value" boxes straight away, this becomes more self-evident by just looking at the UI. The word "trait" is mentioned twice in the text here, but it's not clear what it's referring to if you're not already familiar with segments.
The only situation that absolutely requires an AND NOT condition is if using an operator that does not have an opposite equivalent. As of today, these are only Modulo and In. Matches regex also does not have an opposite, but any regex is trivial to negate. All of these are fairly advanced use cases anyway.
Describe the solution you'd like.
Show the segment creation UI with one empty AND condition placeholder, something like this:
This makes it more obvious what segments are for and lets users define a simple segment without needing to choose between AND or AND NOT.
This also has the benefit of removing the second "NOTE" banner which just looks ugly.
Describe alternatives you've considered
We might want to make a larger redesign of the segment condition editor as described here #4000
However this issue is a quick win that can be implemented today with the current UI.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This is the UI to create a new segment:
To proceed, users must choose between "Add AND Condition" or "Add AND NOT Condition". I don't have data to back this up, but I would guess the vast majority of users will start by creating an AND condition. For unfamiliar users and demos, this masks what segments are for - if we showed the "trait" "condition" "value" boxes straight away, this becomes more self-evident by just looking at the UI. The word "trait" is mentioned twice in the text here, but it's not clear what it's referring to if you're not already familiar with segments.
The only situation that absolutely requires an AND NOT condition is if using an operator that does not have an opposite equivalent. As of today, these are only
Modulo
andIn
.Matches regex
also does not have an opposite, but any regex is trivial to negate. All of these are fairly advanced use cases anyway.Describe the solution you'd like.
Show the segment creation UI with one empty AND condition placeholder, something like this:
This makes it more obvious what segments are for and lets users define a simple segment without needing to choose between AND or AND NOT.
This also has the benefit of removing the second "NOTE" banner which just looks ugly.
Describe alternatives you've considered
We might want to make a larger redesign of the segment condition editor as described here #4000
However this issue is a quick win that can be implemented today with the current UI.
Additional context
No response
The text was updated successfully, but these errors were encountered: