> I UNDERSTAND why you say that, Poutnik, but it is still HELPFUL
> to know what OTHERs like.
I do agree.
What they like,
or what *they* consider the best.
"What *is* the best"
is often forbidden question on moderated SW discussion forums
for a good reason to avoid flame wars.
The best attribute never involves the evaluated SW alone,
but includes people opinion,
so asking which one is best does not make sense.
> That's why I ASKED which passwd manager people like.
You asked which one is best,
but with probable intention
which one they like. :-)
You may wonder what different personal reactions
may be caused by different formulation of the question.
>
>> One of important features for me the K2A has,
>> is its own keyboard, what makes entering the master DB Little more
>> secure.
>
> Hmmm... I just tested these three for which "keyboard" they use:
> 1. KeePass2Android Offline (ad free, open source, offline only)
> 2. KeePassDroid (ad free, open source, offline only)
> 3. KeePass DX (ad free, open source, fingerprint unlock)
>
> All seem to use the _same_ (i.e., default) keyboard.
> At least by default they do.
You may have do too shallow tests.
They use the same default keyboard,
as there is the Android limitation for them to change it on their own.
The *user* has to switch the keyboard himself for security
reasons. It us often possible from Android notification
field
when a user is at text input fields.
>
> Is the problem that Google (or whomever) can be reading
> our keyboard keystrokes?
With your privacy concerns, I expected yourself to be more
concerned then me.
It does read our keystrokes to improve typing suggestions.
But there is another reason, as K2A kbd contains K2A specific
features.
>
>> And, the full, record level DB sync,
>> similar as Keepass2 for Win has.
>
> By DB sync, I assume you mean "merge"?
I agree terminology is confusing.
The generic term sync means getting the same content on both sides
with the latest items(PW records in KDBX context)
The generic term merge means to combine the latest items from both
sides into a single output.
Therefore Keepass2 for Win and K2A perform a sync, while KeePass
XC performs a merge.
The sync in KDBX context means
Both KDBX files exchange latest PW records.
>
>> Very handy is the fast unlock feature ( once dB is open by full
>> password, then if locked, just last 3 characters are enough, with
>> 3 attempts to full PW request). This fast unlock can have
>> alternative as finger print reading.
>
> I think the top 3 have that, don't they?
Good to know, I do not know the other 2 ones.
I just said what I like on K2A.
I use it for multiple years,
so I do not remember why I have chosen it.
I think searching for a good software is like searching for a
future wife.
One should stick at the one that is good enough for him,
instead of longing for the Holy Graal of finding the best one.
>
> I'm asking the group (
comp.mobile.android) which they prefer
> to help us decide on which of the three to keep & which two to delete.
This is what I have originally meant by following the horde.
Result of your priority evaluation
should not depend on what product or features others prefer.
It should help mainly just in awareness of existence of a product
or presence of a feature.