elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.72k stars 8.13k forks source link

[Lens] Product messaging and iconography #192215

Open andreadelrio opened 1 week ago

andreadelrio commented 1 week ago

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 as Lens while ES|QL Lens is simply shown as ES|QL but it uses Lens too. This is inconsistent and could lead to confusion in users.

Open questions

Places where we use a Lens related icon

Data views Discover

Image

"Add panel" flyout in Dashboards

image

"Add visualization" modal

Image 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

Image

Related to https://github.com/elastic/kibana/pull/186867

MichaelMarcialis commented 1 week ago

CCing @teresaalvarezsoler, in case she has any strong opinions on one consistent approach.

elasticmachine commented 1 week ago

Pinging @elastic/kibana-visualizations (Team:Visualizations)

ryankeairns commented 1 week ago

Additional points of consideration:

  1. The term Lens seems to only appear in the global search - if you know to type it - and in the Visualization Library modal (seen in the issue description, above)
  2. We don't refer to it as Lens even within our main navigation or the app itself:Image

+1 to a more standard, shared visualization icon... knowing that Lens is the default editor and the term Lens is mostly insider lingo.

teresaalvarezsoler commented 1 week ago

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.