I know this has been covered in the past, looking at forums back to 2015 (Amazon banned existing personal APIs) and 2017 (Amazon discontinued whitelisting of drive API). But I wanted to know whether there has been any update now that we are in 2020, regarding the possibility of end-users to code, for their own personal use, their own Amazon Drive api.
Not to sound too harsh, but the services the Amazon Drive web interface offer today are rather limited, slow and very unstable (my internet connection is not necessarily the fastest, but should be decent enough for uploads/downloads). Among those:
(1) no possibility to perform any sort of file management (basically looking at a "dump" of existing files in sth as basic as a csv), that could inform the owner of what is on its drive, and what is not.
(2) Linked to frustration created by (1), I am still amazed of how long AD eventually realizes the same file already exists in the upload folder location, and after that candidly asking what should be the next step: this makes uploads really long in inefficient.
(3) a super slow explorer interface in general which makes the navigation rather irritating.
The above (1) and (2) issues are the reason I am today thinking of alternatives ((3) is merely a reflection of the fact that one cannot do anything without the interface at present), but I wanted to understand whether anything was in the pipelines to keep me hopeful there is a brighter future (for example, package libraries provided by Amazon, in the same vein I believe Dropbox did (still does?), if indeed it's confirmed there is no appetite to open to end-users).
If there has been developments on this front, and Amazon has opened again the possibility of end-users to develop their own api, apologies for not having seen it, but could you please redirect me to the documentation?
Thank you very much for any light you can shed on this.