80 karma · joined October 10, 2014
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?
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.
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.