[graphnical]

Haha... yea... so I looked at the API for like 2 mins then the code examples... and was trying to find the justification for the 'We provide you with hosted, secure, reliable, and scalable APIs' part... all I saw was a msging api... so I started thinking all deep like... is there some other part that generically talks to any api... and this is some architecture that organizes the other apis... like 'channels' & 'messages'... hahaha... then I was like... the hell... and RTFCs.

XD

Perhaps, if you plan on other APIs that's cool but give indication that this is just one... give it an icon or something... and then a 'coming soon' icon... group 'em up in a section called APIs.

GL!

[spladow]

Thanks. This is good advice.

May I ask what you thought of the messaging service or what APIs you'd like to see next?

[graphnical]

I guess the idea is that these are utilities right?

You have msging and mention identity, assets storage...

So really this seems like it is heading toward the basic functionality of a CMS...

So... you might end up building some cloud-backed framework to demonstrate the bundle of APIs... that might not be your focus but people could build upon it...

Which is fine if that is what you want to do... another possibility is to branch into APIs covering novel functions.

Given your pricing model, seems you are going for widespread use that leans toward the more generic APIs...

I guess the question is... what do you want spire.io to be in the near future? That would dictate which APIs come next.

Have fun with that ;)