I have recently developed a concept in my mind to modularize the application a bit. Until now, the main view of the application was only one - the list of documents and the preview on the right. I have decided to include the application settings in the main application view as well (instead of a separate window as before). In the upcoming version, icons will appear in the top bar to switch between the document view and settings.

A new feature that will appear in the next version of Keepmark will be Unread Documents. The functionality is inspired by email clients, where new messages are marked as unread. In Keepmark’s case it will work in a similar way and will apply to documents provided from external services.

Starting work on the current version of Keepmark, I had a slightly different picture of the final stage. However, at the moment, one of the biggest priorities for me is to go through Google verification. In version 1.17.0 it took a lot of time to rework email synchronization and introduce additional API for Gmail.

In Keepmark 1.17.0 I am also working on support for AES encryption. This is symmetric encryption - with the use of password. The process of encryption and decryption is much faster than GPG/PGP encryption (which was introduced in the application earlier).

At the end of last year, Google introduced changes in the rules of access to user data. So, after the release of version 1.16.0 I started to apply for verification of the application in Google in order to ensure that users of Keepmark do not see a message about a dangerous application when signing in. After sending the request, I received an answer from them:

(…) To proceed with the verification process, you’ll need to migrate off of SMTP protocol to use the Gmail API. We recommend that you use the https://www.googleapis.com/auth/gmail.send scope, which is sufficient to implement your project’s functionality.

To proceed with the verification process, you’ll need to migrate off of IMAP protocol to use the Gmail API. We recommend that you use the https://www.googleapis.com/auth/gmail.modify scope, which is sufficient to implement your project’s functionality. (…)