Problems with the option to unblock with 4 digits
I love you app (Windows and Android versions) so I decided to buy the PRO. I would like to report some points that I thing could be fixed.
Using the option (on Windows app) to unblock with 4 digits I observed a problem. The correct is to offer only one opportunity to type correctly the 4 (first or last) digits of the password. But, instead of that, after you type wrongly the 4 digits you can press ESC and try again the 4 digits. I think the correct is, after you type wrongly the 4 digits of the password you MUST type the full password to unblock the app.
Provide an option to wrongly enter (first or last) 4-char password more than just once before requiring that the full password be entered. It's too easy on a tiny phone keyboard to accidentally enter a wrong character on the 4-char and then be forced to enter full long password. I'd like to set an option to allow two or three "guesses" before the program falls back to requiring the full password.
BTW, good implementation of using a full/long password for the *actual* encryption and only providing a temp short 4-char under temp limited conditions to access the encrypted dB that has been opened with the full password. As the Apple situation shows, the only way to fully protect encrypted data is to use a long complex password as the *real* encryption password (vs. a four or even six all-numeric password) and not depend on hackable software to limit guessing.