Great transition for implementing own S3 upload Filepicker is a nice tool for uploading files - we use it to upload to amazon S3. For now i am really happy with using filepicker but there are two minor flaws and one show stopper (specific for our B2B customers) which let us change to an own implementation. The first flaw is that i can not use S3 in frankfurt because of filepicker not supporting the AWS Signature Version 4. The second is the poor interface for uploading from Google drive - it is hard to navigate to your files. What really causes the pain for leaving is rather a problem of our customers. The bigger companies we are working with are blocking filepicker within their proxies. Overall we are still satisfied =)

Poor cropping options and urls. Our main issue has been using the images, the cropping api is a poor substitute for having control over your own images. Poor mobile experience. It would also be useful to have full control over the url that is given out on the links (even if it just says not file picker).

Great potential, needs some fleshing out The acquisition aspects of filepicker are great, and my team is happy about the speed with which I was able to allow our users to incorporate Instagram and their ilk. However, I've had slow response from service, often taking several days to get a response since it had to go to the engineers (seems there's a breakdown in that process). The file service and conversions functions are still too limited. I don't mind having to securely sign my API calls, but having to sign query string file conversions is... odd. Cloudinary got around it with their preset system, and better permission management. As is, I'll likely have to use filepicker to send to s3, then have cloudinary grab the s3 links, which is hardly an efficient methodology and involves 3 services just to display images.

Great Tool & Time Saver Filepicker was a great way for us to let our users leverage their photos on other social accounts they have, but also, provide a very simple way to upload content to our CDN. Also, it saved TONS of time to not have to write all of this code ourselves.