Redesign Space Selector page to handle a large number of spaces more easily

[cjcenizal]

When there are a large number of spaces to select from, the space selector page becomes unwieldy (see screenshot below):

• Cards require scanning in a left to right, top to bottom, zig-zag fashion which makes it difficult to compare spaces
• Cards are large with a lot of empty space, which limits the amount of information on screen for scanning and comparison
• Wasted space to the left and right of the cards

Some information that's also missing from this:

• Name of space creator
• Date the space was created (helpful for identifying recently created spaces)
• Date the space was last accessed by the logged-in user

I think a designer could take a couple passes to optimize this page for a couple use cases:

• Helping the user visually acquire spaces that they tend to use most often
• Helping the user visually acquire spaces that they've recently created
• Helping the user sort, search, and filter spaces

My suggestion would be to split this view into two levels: a primary level consisting of cards for the user's last 5 or 6 most recently used spaces, and a secondary level consisting of a table ordered by newest spaces to oldest.

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)

[legrego]

Thanks for opening this and sharing your thoughts, CJ. We've been discussing this with @ryankeairns and @snide recently as well. I think there's broad consensus that the space selector is a bit lacking, and should be re-imagined to provide a better user experience.

[ryankeairns]

Adding to Larry's point, it may ben something quite different than just tweaking this page.

@alexfrancoeur @MichaelMarcialis Regardless of what is decided with the latest home page ideas, we should strongly consider prioritizing this piece of work.

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)

[ryankeairns]

@MichaelMarcialis I chatted with @snide and, if possible, let's see if we can devote some time in 7.16 to address some of the issues outlined above. Namely, the scalability and perhaps some indicator of 'size' (e.g. # of objects, # of indices, etc. - not sure what is available here).

[ryankeairns]

Wireframes based on latest review feedback.

Putting this project back on shelf until re-prioritized; likely after the user entity project makes progress as the use of user profiles would benefit this experience.