Few feature improvements

[flyingbirds]

add delete button for quick deletion of unwanted fields (mockup)

 

The amount of pre-configured websites for a new login is unnecessary. Getting the favicon from the website via the url field is enough.

 

No reason to have a pre-set field type. Fields are either going to be string, number, or bolean.. maybe date but thats it. Autofill can pick up frm the Field name.

 

 

 

[Abhishek Dewan]

Hi @flyingbirds

Thank you for your valuable feedback. I have taken note of your comments and shared them with our dedicated team for thorough feasibility checks and careful consideration. Your patience during this process is greatly appreciated.

#SI-3442

[Bachsau]

Please don't follow these bad suggestions. They are very ill-considered and a good example why following customer feedback isn't always right.

 

On 8/18/2023 at 4:50 AM, flyingbirds said:

add delete button for quick deletion of unwanted fields (mockup)

Unnecessary because you can always create a custom template if you wanted less or other fields. At least such buttons wouldn't be harmful, unlike your other suggestions.

 

On 8/18/2023 at 4:50 AM, flyingbirds said:

The amount of pre-configured websites for a new login is unnecessary. Getting the favicon from the website via the url field is enough.

Definitely not. Many sites don't serve appropriate icons and Enpass only caches those icons but doesn't save them as part of the items. I use a lot of custom imported icons and am always happy if there is a pre-made one.

 

On 8/18/2023 at 4:50 AM, flyingbirds said:

No reason to have a pre-set field type. Fields are either going to be string, number, or bolean.. maybe date but thats it. Autofill can pick up frm the Field name.

Field names may vary and I don't want to be forced to name my fields after some specific schema. I have username fields named "Customer Number", for example, because that is what I login with on that site. Also english isn't the only language in the world. The freedom Enpass gives me with the fields was another reason for me to switch from 1Password. Instead, some field types should have a more strict typing, because currently you can enter any sort of information in a "Numeric" or "Date" field.

Edited August 23, 2023 by Bachsau

[Johnmelody]

On 8/23/2023 at 4:01 PM, Bachsau said:

Please don't follow these bad suggestions. They are very ill-considered and a good example why following customer feedback isn't always right.

 

Unnecessary because you can always create a custom template if you wanted less or other fields. At least such buttons wouldn't be harmful, unlike your other suggestions.

 

Definitely not. Many sites don't serve appropriate icons and Enpass only caches those icons but doesn't save them as part of the items. I use a lot of custom imported icons and am always happy if there is a pre-made one.

 

Field names may vary and I don't want to be forced to name my fields after some specific schema. I have username fields named "Customer Number", for example, because that is what I login with on that site https://depositphotos.com/bgremover.html Also english isn't the only language in the world. The freedom Enpass gives me with the fields was another reason for me to switch from 1Password. Instead, some field types should have a more strict typing, because currently you can enter any sort of information in a "Numeric" or "Date" field.

Indeed, if you look at each piece of advice separately, you can make some exceptions. But you need to approach each case