title: app.js JavaScript API on Google Drive
body: <p>I'm investigating Google Drive's real-time API. In the <a href="https://developers.google.com/drive/realtime/realtime-quickstart" rel="nofollow">QuickStart Tutorial</a> the JavaScript library loaded is <a href="https://apis.google.com/js/api.js" rel="nofollow">https://apis.google.com/js/api.js</a>. The Drive documentation <a href="https://developers.google.com/drive/realtime/application#step_2_load_the_realtime_library" rel="nofollow">describes</a> this library as the Google JavaScript API loader. This library seems to load the appropriate libraries for the services we need to interact with.</p>
  
  <p>But when looking at <a href="https://developers.google.com/drive/web/quickstart/quickstart-js" rel="nofollow">QuickStart Tutorial</a> for Google Drive (non realtime) it seems to load <a href="https://apis.google.com/js/client.js" rel="nofollow">https://apis.google.com/js/client.js</a> which I believe is the library documented <a href="https://code.google.com/p/google-api-javascript-client/" rel="nofollow">here</a>.</p>
  
  <p>My question is what is the difference between api.js and client.js. They seem to have similar purpose although don't work in the same way. Is api.js for certain Google API's while client.js is for others? Is api.js documented somewhere like client.js is?</p>