Unfortunately, Google will soon remove support for the Google Drive Android API (Application Programming Interface) that we used in TimeTune to make backups to the cloud.
This left us with two different alternatives:
- Migrate to the Google Drive REST API, a more generic version of the API.
- Migrate to Cloud Firestore (owned by Google as well) for cloud storage and device synchronization.
However, Google is clear about the intended use for each alternative.
The Google Drive REST API is a solution oriented to applications strongly related with document management (creating, modifying and deleting documents). Implementing this solution for a simple database backup would be overkill.
On the other hand, Cloud Firestore is the recommended solution to store application data in the cloud. Besides, it allows for real-time device synchronization and provides cross-platform capabilities as well 👍
Therefore, our intention is to integrate Cloud Firestore in a future version. This solution will allow TimeTune to grow in a more robust way and will open the door to further capabilities.
Sadly, this means that starting TimeTune 2.6.1 the application will not be able to make backups on Google Drive anymore 😥 We will only have the option to make local backups.
TRANSFERRING YOUR DATA TO ANOTHER DEVICE
The Google Drive backup option was an easy way to transfer your data to another device. We would make a backup to Google Drive on the source device, and we would restore the file from Google Drive on the target device. That was it.
In TimeTune 2.6.1, you’ll still be able to transfer your data to another device, but it will require a different approach:
- On the source device:
- Make a local backup (Settings / Backup / Backup database).
- Use the Google Drive application to upload the ‘timetune.db’ file located on the ‘Download’ folder to Google Drive.
- On the target device:
- Use the Google Drive application to save the ‘timetune.db’ file to the ‘Download’ folder.
- Make a local restore (Settings / Backup / Restore database).
We’re really sorry for the inconvenience. We keep working to provide better long-term solutions for TimeTune ⚒