HN user

cloudrail

80 karma
Posts19
Comments61
View on HN
cloudrail.com 10y ago

APIs for Innovative AdWords Campaigns

cloudrail
1pts0
cloudrail.com 10y ago

Facebook, Dropbox, Mailchimp, Twilio and More Combined into -One Universal API-

cloudrail
2pts0
cloudrail.com 10y ago

Facebook, Dropbox, Mailchimp, Twilio and More Combined into -One Universal API-

cloudrail
4pts0
cloudrail.com 10y ago

Dropbox, Facebook, Mailchimp, Twilio and More Combined into -One Universal API-

cloudrail
1pts0
cloud-rail.com 10y ago

Show HN: Universal Android SDK to Access All APIs (Dropbox, Twilio, Facebook,..)

cloudrail
5pts1
cloudrail.com 10y ago

What to do when the API you are using stops working

cloudrail
1pts0
cloudrail.com 10y ago

Why we need one API for the Internet of Everything

cloudrail
1pts0
cloudrail.com 10y ago

5 Internet of Everything Kickstarters

cloudrail
1pts0
cloud-rail.com 10y ago

Show HN: Universal API for Twilio Facebook Sendgrid Dropbox Mailchimp LinkedIn

cloudrail
3pts0
www.kickstarter.com 10y ago

MATRIX – The Internet of Things for Everyone

cloudrail
8pts5
cloudrail.com 10y ago

Why you need to start developing for the Internet of Everything. Now

cloudrail
1pts0
cloudrail.com 10y ago

Show HN: One API to easily integrate multiple clouds or IoT devices in your app

cloudrail
13pts3
news.ycombinator.com 10y ago

Ask HN: What RESTful APIs do you use most?

cloudrail
1pts0
cloudrail.com 11y ago

Show HN: Meta API for Google Drive, Dropbox, OneDrive and Box

cloudrail
21pts6
instantcryptor.com 11y ago

Show HN: InstantCryptor – File Encryption Web-App for Dropbox and Google Drive

cloudrail
6pts4
www.cloud-rail.com 11y ago

Show HN: JavaScript and Node.js API (Library) for Dropbox, Google, OneDrive and Box

cloudrail
11pts5
www.cloudrail.com 11y ago

Show HN: JavaScript and Node.js Library for Universal Access to Cloud Storage

cloudrail
4pts1
cloud-rail.com 11y ago

Show HN: One Adaptive API for Dropbox, Google Drive, OneDrive

cloudrail
71pts43
cloudrail.com 11y ago

Show HN: The vision of a single universal API for all services

cloudrail
10pts5

Author of that blog post here: Thanks for posting it on HN and all that feedback. We wrote this post to provide a nice overview about good libraries our developers stumbled across the last years. So it is definitely not complete and I'm sure that I missed several great libraries. If you have suggestions, please comment here with the library name, quick description and link and I'll add them to the list. Thanks!

Thanks!

1. Xamarin support is heavily requested and we are working on it. Unfortunately I don't have an exact release date yet.

2. That is a very interesting point. Let me discuss that in our team and I'm sure we will come up with a solution. So basically you charge a one time fee for the app and then go back to them if an update is required and charge again for that?

The library sends statistical data back to CloudRail to provide statistics and notifications for required library updates. We handle this in a way that the library still works even if the CloudRail server is down or slow. The data itself flows directly between library and cloud provider. Currently we don't disable libraries because they die anyway without updates eventually.

Yes, our unified interfaces are the lowest common denominator. We provide functionality which is not available among all providers in a separate interface. The only exception are functions where the developer needs to be prepared to get an empty result. E.g. some users just don't set a profile picture on social, so you have to handle it anyways.

Good question, thanks. You are right, in case CloudRail goes down no one will maintain the libraries anymore. Despite the fact that we won't go down :), you have to ask yourself if the risk is really that big? The service definitely saves you time now and for the next X years. How many time would you invest during that period with native integrations? Definitely one by one SDKs to integrate and I bet some of them need to be replaced as well. E.g. Dropbox from v1 to v2 was a complete new API and SDK. I think integrations need to be maintained anyway and in the worst case (CloudRail goes down) you have to invest max the same time compared to manual. We love open source and this is an option as well.

1) What APIs has your team built before that qualifies them to build this?

Our team has been in the API business for 4 years now with a lot of different projects and products.

2) How will you manage changes, bugs, and obscure documentation issues in the APIs that will be made available through you?

We have a system called API Change Management. Every connected API is monitored for changes. Once something happens or is announced we update our SDKs and put that information back in the system. Afterwards the system checks all SDKs which are implemented by customers and which integrations they use and automatically notify affected ones by email and via our portal. .. 4) What language will the API be written in?

Currently we support Node.js, Android, Java and iOS (Swift & Objective-C)

5) Regarding API access security: How will you handle access to multiple APIs for the same client when each API requires a different set of tokens?

We let customers use their own API credentials which they get directly from the providers.

You are right, in the end it is a trade off. CloudRail has no down times, can't touch your data and is as performant as a native implementation. But yes, in case of an API change you have to update the SDK. We have a notification system though. You will get an email if you are affected by a change.

An API to the APIs 11 years ago

Thanks for your feedback. We'll definitely put a focus on payment APIs. Each available service in CloudRail needs to be defined once either by us or usually by our community or the API provider itself. If an API changes, the definition needs to be updated as well. After that you'll get a notification and can update your integration as well with just a click. So to answer your question, it depends how fast the community reacts on changes or if the provider cares about the definition itself.

[dead] 11 years ago

As I said, it is a completely new service just under the same domain. The community is interested, so tell me how should I post it here to not get a flag? I'll do it exactly as you tell me.

[dead] 11 years ago

The significant discussion was about our first version which was made just for cloud storage. Now we launched with a generic API and the opportunity for the community to add services as well. The whole thing is even for free... Think that really fits to Hacker News.

[dead] 11 years ago

ok... I will not delete anything again and resubmit with the original cloudrail.com domain. But then you have to upvote :)

[dead] 11 years ago

Again via the official CloudRail account and "Show HN". This is a repost because of a previous flag. We think it is an interesting topic for developers and hope to not get flagged again :)