Originally, when I started working on [Fileshark](fileshark.app) I designed it around using your own Google Drive as the storage backend. I ended up going in a different direction. Here are some of the reasons:
- Having the entire product be reliant Google is just too big a risk. Google has changed apis, and restricted access to third parties.
- Lots of added complexity around search, pagination, etc.
- Due to the last point, all the files need to be tracked in an external database. This adds a requirement to keep everything in sync.
- Now that the files are not stored in Google Drive, I’m working on adding an option to support auto backups to Google Drive.
Comments
Originally, when I started working on [Fileshark](fileshark.app) I designed it around using your own Google Drive as the storage backend. I ended up going in a different direction. Here are some of the reasons:
- Having the entire product be reliant Google is just too big a risk. Google has changed apis, and restricted access to third parties.
- Lots of added complexity around search, pagination, etc.
- Due to the last point, all the files need to be tracked in an external database. This adds a requirement to keep everything in sync.
- Now that the files are not stored in Google Drive, I’m working on adding an option to support auto backups to Google Drive.