This is really nice work, @busradegirmenci! And you obviously put some time into it, which is very generous of you.
If I may offer you some ideas/requests to consider (I’m a UX designer, so I tend to stop at the wireframe stage before UI design experts such as yourself take over!):
-
having an ‘always on’ filter area for the vault would save a click as well as reduce cognitive load. It is described as idea 1 in this post, and could be a helpful evolution for your concept. This is a useful feature for people with larger vaults because typing a couple of letters is faster than trying to scroll and stop, plus it means one doesn’t have to remember the first letter of a vault item in order to find it in the alphabetical list.
-
reducing the padding between data rows (either by removing whitespace or increasing font size; the latter approach may help to retain a large click-area per item) could also help interaction with large vaults. You could consider having 2 different padding options: one value for ‘vault data row’ and a larger value for ‘menu options’ (such as the vault item category list, or the other configuration menu areas) as this could help consistency as well as handling the needs of these different interaction element types.
