Why Ahoyo?
by Paul Kinlan
What we know as "the web" is constantly evolving. In recent times we have seen the emergence of blogging, then videos and now micro-blogging. Whilst the popularity of each of these types of services varies over-time (for too many reasons to list), each has one common facet: they allow instant publication.
It is hard to say if the demand for instant publication is driven through the demand for instant consumption of information, or consumption of data is driven by data being available immediately. Regardless of which comes first, consumption of data can be categorised into two distinct groups: near real-time and everything after that (next hour, next day, 2 months later, 3 years ago).
Applications built through the Ahoyo framework can take advantage of these Real-time streams of data. The Ahoyo infrastructure is pubsubhubbub aware (if you don't know what pubsubhubbub is - think of it as "don't contact us, we will contact you.", that is as soon as data is available from a source we will be told about it rather than have us check every 20 minutes).
Now that data is becoming available in near real-time, wouldn't it be nice if you could create and deploy your application to smart-phones in nearly the same amount of time that it takes for the data to be published?. Thats where we come in, we can build and deploy* your applications at super quick speed.
*Apple have approximately two week turn-around time for approving applications. Apps built for the Android marketplace can be deployed nearly instantly.
