All users (including Premium and Free subscriptions) can set up a free organization vault, with up to 2 collections. If you want more than 2 collections (i.e., more than 2 “tags”), then you will need to pay for a Family plan or a Teams plan (both $48/year).
Please refrain from making unsubstantiated accusations (which violates forum rules). Collections are sophisticated structures that are primarily used for managing access control to shared vault items; you can read about collections here, here, and here. It is just a coincidence that the ability to associate organization items with multiple collections also makes it possible to use collections as a way of simulating tags. It would make no sense to rename collections to “tags”.
On the other hand, if Bitwarden moves ahead with the development of what I’m calling “superfolders” (which would allow items to be associated with multiple such folders), which is what was hinted at in the comment by @gtran, then “superfolders” = “#tags”, and I would see no reason not to rename this functionality.
The Collections construction is, in my opinion, not really user friendly, and far away from the idea of using it for “#tags” like we know it from other apps. First, I have to create an Organisation (I use BW as a private person, so I never thought about to set up an Organization account). 2 Collections are free. And then to understand how Collections, Organisations and Sharing items works? I am a private user (without Family account). For me, this method is too “complex” for just adding something like #tags. Maybe I misunderstood something, but this might underline that it is too “complex” for me.
In other apps you just enter a word in the field for #tags and: Done.
“almost as good as real tags”, not equally good. There is a feature request to bring search parity to the mobile apps. Feel free to vote for it.
That said, iOS does search the URI field today, so you could add your #tags to a URI field and set the match detection to never to prevent the “tag” URI from being considered for autofill.
If you find it offensive, you are not required to use it. It’s a workaround for those who find benefit in being able to mostly-simulate tags on mobile apps before they are formally developed without polluting the highly-visible “name” field.
No, not offensive. I was just surprised to learn about the idea of using the URI field for #tags. I would have never thought about using it for #tags because a field for the URI is for the URI.
It is a question about UI design, and - I agree with you - adding a tags field next to the “name” field” would not be a good idea. In many apps #tags are placed at the bottom of the item/object. Not sure why you mention “highly-visible” (name filed) - do you mean to add more information to the name field? Just wondering …
I would use #tags for e.g. various projects or clients, persons, members of family, …. I want to keep the name/title as short/clear/simple as possible. And here it would be nice to use additional (and real) #tags like #project1 to see clearly that this item is relevant for Project 1 only. Yes, there are always many ways to get to Rome (a German saying) and until now I always found a way to organise my items (like here in Bitwarden) - with or without #tags. But with #tags it would be far easier and user friendly.
What I have learned here during the last months/years is that Bitwarden is an app which has a strong focus on backend and safety, technically spoken. And not (so much) focused on a user friendly UI or how to “interact” with the common user. For me, knowing that Bitwarden has not added #tags or pre-defined item types, or using mainly blue and white (and some black) in design of the apps/UI or website underlines this “philosophy”. On the other side it is also a good way to differentiate or distinguish the product Bitwarden from competitors e.g. 1Pwd or Enpass.
General question: Is there a text or a page where we can learn more about the vision, the idea or philosophy of Bitwarden? Where the developers (or CEO, core team, …) explain a little bit more about their idea and vision.
Background of my question is to understand why basic features like #tags or pre-defined items are not implemented - for years now.
There is this blog article, where the CEO outlines their vision:
No vision statement is going to go into this level of detail (including the one linked above). For Bitwarden’s near-term development plans, your best bet is to consult the public development roadmap.
Obviously unfortunate, that the feature didn’t make it back then. (for whatever reason)
At least one thing to consider here: back then, the roadmap contained a section for features that already were in development and a section for features that would be in research only. (this was changed some time ago to a roadmap that only shows items in active development, probably because of things like these here…)