Why Is OneDrive (API) So Convoluted, Complicated, and Documentation that Leads to Circular References of More of the Former?

  • Thread starter Thread starter Tritonal
  • Start date Start date
T

Tritonal

Guest
I'd like to incorporate the use of this feature in my app, as I have already done with Google Drive (absent confusing and complicated API references, tokens, and unnecessary method calls). Google Drive was simple and easy to integrate. In contrast, the OneDrive API has changed its names more times than people change their mobile phones. It's frustrating and downright un-Microsoft-like. Did they outsource this to some wonko vendor? Why do we need to know all this stuff about Drives and DriveItems? Who cares? Why should we believe or be made to believe a drive on the cloud is any different than

Continue reading...
 
Back
Top