Human.io's job is to sell the developers. The developer's job is to sell the humans. I think I have that right.
Imagine if the Chicago Tribune wanted to build data-driven apps from people on the streets downtown. Just like if they wanted to do telephony apps they'd have to spend $300k getting Asterix wired up properly and Twilio makes it work out of a Sinatra app; similarly, my sense is, Human.io is trying to do that for people-driven apps.
This is exactly correct. We need to make it easy for developers to sell the humans.
(In my parlance, publishers are the people with audience, developers are the people who code, and audience are the people that use the phone. In the wacky future, they may only be indirectly connected.)
It's like the question you're asking developers is, "what if your app could be on every block in Chicago, in real time, right now? What would you do with that?"
Also, I think the emphasis on "humans" in your messaging obscures the point a little. You're not so much programming humans are you are transforming them into sensors.
In that sense, a little surprised the words "eyes and ears" appear nowhere on your front page.
Imagine if the Chicago Tribune wanted to build data-driven apps from people on the streets downtown. Just like if they wanted to do telephony apps they'd have to spend $300k getting Asterix wired up properly and Twilio makes it work out of a Sinatra app; similarly, my sense is, Human.io is trying to do that for people-driven apps.