Galaxy of Emptiness

Entries from October 2007

How Big is My Audience?

October 31, 2007 · No Comments

As reported in the NY Times, the debate continues about measuring web properties. It was perfect timing for me because, I was chatting with Robert Scoble at Web 2.0 about the size of the feed reader audience. Unbeknownest to him, I obsessively attempt to track the core feed reader segment (Bloglines and Google Reader.)

The NY Times article surprised me because, I didn’t think that the debate continue for top tier web sites. Surely, they are big enough and don’t have large discrepancies. I thought, most of the panel based approaches are fairly good at measuring at audience size. But I guess I’m wrong. For example, Forbes.com claimed 11.6 million United States visitors last month. Yet Nielsen/Netratings only counted 7.5 million and Comscore estimates were even lower, 5.8 million. The case gets even worse for smaller sites which can’t rely upon third-party measurement.

The problem is an old one for sites without registration. These sites track unique browsers which is some major flaws. The first is that I might use multiple browsers (PC and Phone. Or Laptop at work, Desktop at home, Phone and iPhone.) The second is that I might upgrade my browser which would count as two unique browsers. In short, the tracking of unique browsers needs to get collapsed to unique users. Withou a required unique user id, it’s difficult to be sure that a specific user is using a specific set of browsers.

Over the next couple of weeks, I’ll write a series of posts outlining the different data available from the various services and outline some of the caveats. I think this is important because most of the tech bloggers are comprised of independent developer types who generally don’t have access to paid subscription data services and therefore have probably not delved into the details of the services.

Categories: Uncategorized
Tagged: ,

Business of API Conference Notes

October 16, 2007 · No Comments

Yesterday, I was at the Business of API Conference where I ran into some old friends and new friends. Outlined below are some of my notes before I had to run and take off.

The key summary to me highlighted by several, but really brought home by Dave McClure. Your API strategy needs to be in alignment with your Business Strategy. I.e. Your API strategy needs to have your revenue model backed into the APIs.

 

Oren Michaels, CEO Mashery
Requirements for Successful APIs Infrastructure

- Reporting – who’s doing what?

- Monitoring – proactive ability to throttle or manage users to their appropriate service levels.

- Scalability – need to handle the vastness of the developer network

Twitter – 10x times as much traffic coming via the API than the front door traffic

An Aside from an Intuit employee -

67,000 developers with access to a synch API. Imagine what they will do with a full set of APIs.

 

Thomas McCarthy Howe, Consultant

A quick primer on generalized anxiety disorders. Hmm.

- Expectation of the worse becomes habitual behavior.

- You do not know how your APIs will be used. Let go.

Round Table Discussion

Quentin Hardy, Forbes
Jeff Barr, Amazon Web Services
Michael Jones, Userplane/AOL
Bradley Horowitz, Y!
John Richards, MSFT

Y!
Flickr example, APIs enabled flickr to be distributed by the blogosphere.
Many of the Y! web acquisitions are badging APIs and not deep integration APIs. Badging was not a common practice 5 years, but has become the dominant model.
12-18 months vision – reduces ramp-up costs which distr

AOL
Extend services to 3rd party websites and then drive advertising models.
Moved from a fee model to a free advertising model with revenue share which also creates a need for fraud prevention.
12-18 months vision – many companies will need to move beyond APIs to real API strategy with monetization

Amazon
265,000 users in the web services community
Developers were already scrapping the data from the website to build sites which would send traffic back to Amazon.
Cost following model used to developing pricing for the web services.
12-18 months vision – radically reduces ramp-up costs

Asha Vellakial
Telco 2.0 – under attack from disruptive services and governmental regulations
Open APIs have concerns for Telcos such as risk to the billing relationship with the customer.
BT is the leader with APIs
Bobbletop – news aggregator
Wants more Open APIs from aggregator companies. I followed up with here afterwards. I’m still not quite sure what she meant by this other than the telco content experience should be more open.

David Cancel, former CTO Compete
6 months of open apis was greater than 6 years of marketing

Jia Shen, Rockyou
Positioned as the Social Platform API
Facebook is 7x the growth of Myspace – this is the seond time in a week to see that message. Look to see more direct comparisons of social networks going forward.

Dave McClure, former head o PayPal developer network
7 habits of highly successful developer programs
- audience - get one.
- product – better be cool, code examples in cool languages
- geeks – hire geeks, extroverted blogging geeks
- metrics – most important thing – “have some”
- biz model – api must have the business model built-in
- education – make it free and easily accessible
- marketing – sell the developers – give them respect

Categories: Uncategorized

Size of the RSS Audience

October 16, 2007 · No Comments

Due to some reporting outages by Google, some of the blogerati are questioning the size of the feed reading universe. There are number of false assumptions.

- consuming services are all feed readers.

- all subscribers are active

- subscribers between consuming services are unique

The biggest consumer of RSS/Atom is iGoogle which now accounts for 20% of Google home page traffic.

A subscriber doesn’t necessarily interact with the feed. Even if the subscriber does interact with the feed, it could be a very low level of interactivity.

Users can subscribe to multiple feed readers or consuming services.

Categories: Uncategorized