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.
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 ;)