3 ms·
One cool thing I did with the Google Drive API was pull in our app's release notes from Google Drive. This allows our product and support teams to write/edit re
by leesalminen 8y ago
One cool thing I did with the Google Drive API was pull in our app's release notes from Google Drive. This allows our product and support teams to write/edit release notes and have it "magically" appear in-app as HTML. The workflow is:
1.) Employee creates a GDoc in a known, shared folder
2.) Application pulls all GDocs from this shared folder
3.) Application uses GDrive API to convert the GDoc to HTML
4.) HTML is displayed to the end user.
This proved to be an easy solution to having to involve a developer to fix a typo in a release note.
- nolite 8y agoI did something similar and hacky by just rendering the google drive links in an iframe in our app
- seanwilson 8y agoDo you have to worry about abuse of the API key used to pull in the doc or this isn't an issue (e.g. API call cost or going over a quota)?
- leesalminen 8y agoWe do 2 things: 1- the API keys are only used on our servers and not the device, so no new worries about the key getting out and abused 2- we cache the results of the API calls for 5-10 minutes with Redis. So there's no worries about the quota or rate limits. We've been doing this for about a year with 15,000 daily active users. When we publish a new release note roughly half read it within the first 24 hours. No issues to report.