I've looked around your site, and I'm still not sure what you offer. I've figured out that you offer APIs, but APIs that do what? Push messages (urban airship)? Search (indextank, searchify)? Geostuff? Video encoding (zencoder)?
I could probably dig into the example libraries and figure it out, but if people don't figure out what you offer pretty quick, many will bail.
This is definitely constructive. The fact that aeontech and ecaroth both had the same issue means it's clear that we can improve how we explain what we do.
Right now, the only API we have is secure real-time messaging. We are working on rolling out a bunch of others (ie identity, assets, storage ...) in order to create a more complete solution for developing backend infrastructure.
What kinds of APIs are you most interested in seeing?
Thanks to everyone for the feedback so far. It's been very helpful.
Likewise. Although, looking at the examples made me even more confused: I was expecting to see some code examples showing how I'd actually go about using/accessing the API. But it just showed me an app, which could have been built using a large number of technologies in a large number of ways.
My advice? Show us how this product makes life easier than whatever it is that it's an alternative to.
Same here, I spent 5 minutes reading 'Get Started', and still couldn't make heads or tails of it, so went back to HN to see if the comments here make it any clearer.
Comments
Hopefully constructive criticism here:
I've looked around your site, and I'm still not sure what you offer. I've figured out that you offer APIs, but APIs that do what? Push messages (urban airship)? Search (indextank, searchify)? Geostuff? Video encoding (zencoder)?
I could probably dig into the example libraries and figure it out, but if people don't figure out what you offer pretty quick, many will bail.
This is definitely constructive. The fact that aeontech and ecaroth both had the same issue means it's clear that we can improve how we explain what we do.
Right now, the only API we have is secure real-time messaging. We are working on rolling out a bunch of others (ie identity, assets, storage ...) in order to create a more complete solution for developing backend infrastructure.
What kinds of APIs are you most interested in seeing?
Thanks to everyone for the feedback so far. It's been very helpful.
Likewise. Although, looking at the examples made me even more confused: I was expecting to see some code examples showing how I'd actually go about using/accessing the API. But it just showed me an app, which could have been built using a large number of technologies in a large number of ways.
My advice? Show us how this product makes life easier than whatever it is that it's an alternative to.
Same here, I spent 5 minutes reading 'Get Started', and still couldn't make heads or tails of it, so went back to HN to see if the comments here make it any clearer.
Ditto - this comment mirrored my thoughts/experience exactly