Reading Time: 4 Minutes ReadThis is the first post of my series about working around Google Drive APIs. Google Drive. You can’t really exist on the web without ever encountering it. You are most likely an avid user if you are reading this. Obviously, from the users’ point-of-view it is a great product. With the initial release that happened over 10 years ago — when the currently widely used Drive moniker was nowhere to be found as it was Docs, Sheets, and Slides — it made online collaboration widespread. Due to the tight integration between the various G Suite products nowadays the need for enterprise solutions that use — or actually build upon — it increased a lot. I was lucky — well that is questionable, and you will see later why 😉 — enough to work with it for a rather long time. Well, long time seems a bit over exaggerated given that it’s been only 5 years a few months ago, but due to the age of the whole product, I still feel like a Methuselah. Looking back we created solutions I never imagined we will, but it came with our fair share of mindf*ck along the way. I think Google was surprised as well how popular it became in just a few years. Sure, it certainly wasn’t the view it projected for the users and what you could see in the marketing bs — sorry material — for Google Apps — maiden name of G Suite -, but if you have ever tried to integrate with it you could certainly see the drawbacks and the indications that this wasn’t planned as an enterprise product with a scale like this. After I just wrote this sentence I already heard many of you cry out about how unjust I am with Drive — given that neither of the competitors is better. Well, I don’t think so I am. I just meant enterprise-level integration with a wide feature set and huge throughput, and preferably projects that have started years ago as the issues I’m about to describe resemble the rain forests. They tend to decrease over time. At least, in this case, it’s good news :). Although I already worked with some older services (like Documents List API, Spreadsheets API), and some newer ones (like Drive API v3, Sheets API v4). Most of my experience comes from Drive API v2… and well let’s just forget the GData era. It’s better for everybody. I thought about ordering and prioritizing the issues, but I couldn’t come up with a decent enough rule for it. Basically, every issue could easily be just as crucial to an app as irrelevant it is to another one so I go as it feels right. Also, I’m sure it would have been heavily biased already, as I do remember every single hour that it caused me thinking about my career choices 😀 So excuse me in advance if I might ramble — or even rant -, but that is how I “cope”… it’s cheaper than drinking ;). … and please consider that many experiences I describe here happened before it was documented and/or fixed properly.