Open andreadelrio opened 1 week ago
CCing @teresaalvarezsoler, in case she has any strong opinions on one consistent approach.
Pinging @elastic/kibana-visualizations (Team:Visualizations)
Additional points of consideration:
+1 to a more standard, shared visualization icon... knowing that Lens is the default editor and the term Lens is mostly insider lingo.
Before making any changes, I would like to have a more clear idea for the long-term vision. The proposal is that Lens and ES|QL are merged into one experience with two modes (Lens powered by ES|QL) and the editor is merged into Dashboards and Discover. We are discussing all these possibilities right now so let's wait for the conclusions.
Of course, the long-term vision should consider the icon and wording consistency issues stated here.
We currently support two Lens experiences (1) Data views based and (2) ES|QL based. (1) Is available as a dedicated app and as an inline editor in Dashboards while (2) is only available as an inline editor in both Dashboards and Discover. In our
Add panel
flyout in Dashboards,Data Views Lens
is shown asLens
whileES|QL Lens
is simply shown asES|QL
but it uses Lens too. This is inconsistent and could lead to confusion in users.Open questions
data view(s)
and the two modes (i.e.ES|QL
andData views or Classic)
, could we do the same forData views Lens
andES|QL Lens
? This should be considered as well in the related issue #192197 where we are redesigning the "New visualization" modal.lensApp
logo which many have pointed out is not clear?Lens
(and therefore the corresponding icon) vs avoid using it like in "Edit visualization" with the accompanying pencil icon that we have in ES|QL Discover?Places where we use a Lens related icon
Data views Discover
"Add panel" flyout in Dashboards
"Add visualization" modal
Note: the scenario shown in the screenshot above will be fixed by #192197
Places where we don't use a Lens related icon or the word Lens in the UI
Related to https://github.com/elastic/kibana/pull/186867