This week I want to update you on our efforts in integrating Google Drive into our Tikkun app. As I wrote last month, we decided that Google Drive provided the best solution at present for giving iOS and Android users a way to share content with each other directly through our app. It will also give users a way to sync their own content and app preferences across multiple devices. In order to make sharing and syncing “just work” for our app, we needed to get a deep understanding of how Google Drive operates, and then how to program the desired functionality. So we have been doing a lot of reading and experimenting, learning how to securely log in and out of Google Drive, create, find or delete a particular folder or file, how to use our own custom file types, and so on. (For those with a technical background, we are using the Google Drive REST API.) We have been able to log in and out of Google Drive on both the iOS and Android versions of our app. We have so far only tested out the various file and folder operations on Android. We will soon move on to doing the same operations of iOS.
Another critical aspect of integrating Google Drive into our app is handling any error conditions that might occur. In particular, the app will need to respond reasonably if a file or folder that is requested is not available. This could be because the item was deleted, or because there is no network connection. Further, if a network connection is metered (i.e., it uses data on a data plan), the app should not make that connection without the explicit permission from the user.
Once we have the level of control that we need in both iOS and Android, we will start looking at how to present information about the user’s content on various sizes of screens. We also need to refine exactly what data we need to store for the user, and how best to organize it. User data management is at the core of what will make the app really useful, and it will, undoubtedly, take some time to get it right.