Hello
Please add an option to sort OTPs per their last usage time.
what i mean is like andOTP
Thank you
Can you be a bit more specific? What would qualify as "usage"?
I think he means sending the last entry used to the top.
To send entry top top, it would imply the user reveal or copy the code. In fact, if entries are not hidden and user does not click, there is no way to know an entry is used.
The option should be added to the 'sort by' button, to complement sort by account and sort by issuer.
Thanks @mdmk
@alexbakker I Exactly wanted to say this.
Hiya
I am new to this so I hope I haven't done it wrong. I would also like this feature. I understand the reason why you think it wouldn't work.
For myself, because of the way my brain processes information, I find the list interface very hard to use; everything gets jumbled together; it's very hard for me to find things; once I find them I lose them again. Extremely frustrating and slow. It would be a great imrpovement if when you pressed the item you want, it would become highlighted somehow. Such as becoming bigger, and the colours of all items dimming. If you did that, it would have the side effect of something that could be counted so the most recent could float to the top.
For clearer communication I drew this picture quickly showing the screen as it normally is, tapping on Wordpress item, and how it becomes much easier to read.

Unfortunately I have no understanding of the development environment so no idea hoe easy/hard/possible this would be.
Sorry if this should have been its own "issue", I wasn't sure and like I said, I'm new here. If you give me an issue for my issue I will try to fix it.
What do you think?
Thanks for your clear explanation @CouldBeThis. We have recently made some changes to our interaction (#173) which makes sorting entries by 'usage' possible. The following will be available in new versions of Aegis:
We can now record the amount of usages since tapping on the code will now 'only' copy the code. We can combine this with some 'Dim on tap' preference which will dim all the other codes for a set amount of seconds (i.e. 10/15 seconds). I'm not a big fan of making the entries bigger and I think dimming the rest of the entries will be good step forward.
What do you think @alexbakker? Do we need another issue of the dimming part?
Thank you, I posted this before that change had been made but GH didn't make it visible because they didn't like me email address and it took me this long to get it sorted out.
I'm waiting for the new version to come up on F Droid so I can use it, looking forward to that.
Thank you for being so very responsive that you read my mind. ;)
Hello,
Having updated Aegis from F Droid a few times I was hoping the "last used on top" feature would show up. I thought this was on the way. However, in rereading the last comment by @michaelschattgen I wonder if perhaps I misinterpreted.
Which is the correct understanding of current situation?
A. Sort by last use is implemented, or
B. Something else has been implemented which now makes sort by last use _possible_ but not yet implemented
Thanks for your time in everything.
It's indeed B, unfortunately. We've made changes to the way our users interact with the tokens which made it possible for us to 'track' the usage of each token, we just didn't implement it yet.
However, this feature will be implemented in Aegis eventually!
I agree this would be very, very useful.
I do use the "dim" and "hide" option, so this feature would be totally useful (if either of this option is selected, actually).
Also, it makes it very useful for many entries, because one may not really know what entries are actually used and which accounts are just legacy.
So actually, I would rather propose (another option) to sort by usage count, i.e. most used account is at the top, legacy ones at the bottom. After a few rounds of normal usage, thus the sorting gets useful and the more you use the app, the more it "increases" UX, somewhat…
Because sorting by name or whatever it you currently can do is arbitrary – compared to sorting the accounts you use most/often/recently at the top (so you can access them quickly).
@rugk
So actually, I would rather propose (another option) to sort by usage count, i.e. most used account is at the top, legacy ones at the bottom. After a few rounds of normal usage, thus the sorting gets useful and the more you use the app, the more it "increases" UX, somewhat…
I like that idea. The downside would be that a token that was very frequently used in the past, but is no longer used currently, will stay at the top for quite a while before the other tokens can catch up with its usage count.
Yeah, possibly then reset that token count after 14 days or so? Or calculate some "score" based on "last usage" + "usage count", together?? (You can call that "automatic" or "clever sorting" then :stuck_out_tongue_winking_eye: – marketing works :wink:) You could improve that algorithm endlessly, I guess…
Clearly, the only solution is to apply some machine learning here /s.
Well… you could certainly call it "artificial intelligence" depending on your definition. :laughing:
Another vote for this feature, it's extremely useful when dealing a large set of OTP tokens.
Most helpful comment
Clearly, the only solution is to apply some machine learning here /s.