Hacker News Reader

Comment by kelleyk | Hacker News Reader

It seemed like an aside, but the issue of being at the mercy of the people who provide platforms and other foundational technology really resonates with me.

("Building on top of a platform is a foundational risk, and if your platform decided one day that it doesn’t like what you are doing, or likes what you are doing so much they want to compete with you, it’s Very Bad. Your platform partner can easily damage your quality of service, or simply shut you down. If that happens, your business is dead.")

Have I missed an explanation from Dalton or the App.net crew about how what they're envisioning will be different? What protects a developer from being at their mercy for uptime, timely bugfixes, continued development, and so on?

Actually, on a more general level... what can platform/tech providers do to provide those reassurances? I can't seem to think of anyone who's done a really stellar job of it.

View on HN

In my announcement of this project, I argued that Github & Dropbox are the best examples I can come up with as examples of healthy, innovating platform companies.

I believe our approach is different in that App.net customers are developers+members paying for a service that is provided. This is different than customers being advertisers, and developers+users being treated as a product, or at worst collateral damage.

I think this all boils down to business model choices and financial incentives: http://daltoncaldwell.com/an-audacious-proposal

Both Github and Dropbox offer a free plan plus they don't need the network effect. If I were the only user on Dropbox I would still find it valuable. Same on github.

However the service you are proposing does have a huge network effect. Twitter/e-mail without users is not valuable.

So whats your plan to get to a million paid users?

NOTE: Pandora had about 71 Million on October 2010 but only about 700,000 paying users. So not even Pandora has been able to get to 1 million paying customers. Just look at the financials. 14% of revenue came from paid users and 84.6% came from ad's. Which supports Fred Wilson point that the majority prefers ad supported services.

I am going to support App.net. I still want to see you try. But I am afraid you don't really have a good answer on how you plan to build the network and Fred Wilson is trying to warn because you will probably fail. But something tells me you don't care if you fail, thats why I'll support you.

I think you're wrong to suggest that having developers and users as paying customers qualitatively changes the conflicts between platform users and platform owners.

Even with paying customers you still face conflicts like:

- conflicts between serving different groups of customers (e.g. IIRC, contractors often complain about Github's pricing because it is more adapted to enterprises)

- conflicts over whether or not specific features are part of the core platform (Microsoft and Apple routinely run into this - and virtually all of their users and developers are also paying customers)

- conflicts over priorities/roadmap and so on

At best, having developers and users as paying customers is an additional weight on the same underlying scales.

Reply on news.ycombinator.com