Single Quick Bar #11511
Replies: 5 comments 7 replies
-
Fantastic concept. I confess to barely using the quick bar(s) because having to remember to press a certain letter on the keyboard feels antithetical to an intuitive UX. Having it be a visible button AND combined seems like a logical evolution. |
Beta Was this translation helpful? Give feedback.
-
I really dig how you have it being triggered now using a search button :) This will make mobile users happy and we can remove our workaround in the android app. Currently today we trigger it using a 3 finger swipe down gesture but some devices use that gesture for other thing so not all users can use it. Now it will work across all setups :) |
Beta Was this translation helpful? Give feedback.
-
Like it. But please don't remove the hotkey(s). BTW Wasn't it before one as well? At least I'm able to remove > in the one or add > in the other to search via versa. |
Beta Was this translation helpful? Give feedback.
-
While I like the idea - I would also propose that all of the hotkeys, search functions like #12324 and so on would allow us to turn them off completely for non-admin users. I am my HAs only admin, and I like the features. But I do not want any of my HA users to find out about them. Then I will spend more time locking down HA then using it for new features. I think "back-end information" in HA should be accessible on a need-to-know-basis. Which means I think it should be natural and easy to choose not to have access to Logbook and History (in more-info), hotkeys, global searches and so on. Therefore I would propose that all of this kind of functionality would be limited to admin users. I would really like to have a panel for controlling the devices of my (the admins liking) without needing to reverse engineer solutions to keep other stuff from nosy kids, guests and other users. Anyway, please allow all future shortcuts/quick find solutions to be easily turned off. |
Beta Was this translation helpful? Give feedback.
-
yes, please allow me to chime in, I hadnt seen this yet before I posted: #12384 there is a tendency to see more and more Tips and Magnifiers, which is not really useful for the overall experience by default per se. I for one don't care for the tip we now see in dev tools Set state,(I am there so dont need the tip) nor for the Magnifier in all of my carefully curated frontend Menu bars... Nice to have on keystroke, but not 'always on'. Especially not for the non-admin users, who in my household should never interfere with any backend search. So yeah, I like the search functionality. A lot. But not always on, and Not for everyone. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The Quick Bar is an amazing functionality with lot of potential for every user. This prototype focuses on merging the two separate search bars for entities and commands. Currently you can open an entity filter (hotkey
E
) or the command pallet (hotkeyC
). In my opinion having two quick bars isn't necessary and we could merge them into a single one. Currently our quick bar searches on entities, pages and commands. In this design I've added some suggestions people can search for.For now I've added a search icon on the dashboard to open it, but on another discussion I would like to investigate if it's nice to have a search icon on the sidebar.
Desktop prototype

Mobile prototype

Current Quick Bar

Beta Was this translation helpful? Give feedback.
All reactions