406 karma · joined January 4, 2011
I agree that it is helpful to point out that there are major risks when you develop for an alleged platform. But isn't that the point of his post?
I think the point of the app.net initiative is to create a platform that because of its different business model (subscription for infrastructure/service) will not suffer the conflicts that are inevitable when the business model is ads. And whilst this is indeed unusual lately, it is not long ago that such for-profit platforms were the norm. Older examples include, DOS, Windows, UNIX, Linux, X-Windows... More recently there is a profusion of companies providing commercial support for open source software or providing such software as a service.
a) dev builds software on the platform that doesn't disrupt the platforms economics, distribution, or organizational limitations. b) dev builds software on the platform that does disrupt the platforms economics, distribution, or organizational limitations.
You seem to be saying that if he had done a 'proper job' he would have pursued strategy b. But surely that is precisely the case where you can expect to be bullied. It is strategy a. where you develop software that does none of those things, but adds value to the platform by adding value to the users of the platform where you are least likely to be bullied. In these circumstances you are no threat and you are complementing the platform.
Strategy a can only be pursued when you are not dependent on the platform and hence are much harder to bully.
But what does ‘require a new entrant’ mean here? Who requires it? There is surely only one meaningful answer - the consumer. Moving on... What sort of new entrant offering ‘can not be filled by a product line extension from an incumbent?’ I suggest in the context we should parse this to mean ‘... platform company cannot build a competitive offering.’ But of course, there is little that such well financed companies who control the platform can’t build. More to the point there is still less that can’t build if all they have to do is copy an existing product. So this is a very strong condition. Perhaps you mean - software the platform company doesn't want to build? One answer along these lines is to build software for a small segment the platform company cannot be bothered to address. But for an ambitious developer who wants to add significant value to millions of users I am not sure it is possible to develop such an offering - insulated from potential competition by the platform company - unless the platform company has a clear policy vis a vis developers and provides very clear signals with a very clear record to trustworthy behavior that gives a high degree of confidence it is safe to proceed. But of course developer is taking a risk that the platform company can bait and switch. I am unsure what ‘large companies with developer programs all consolidate their segments’ means. But if it means that such platform companies have an inbuilt drive to purchase their devs I can’t agree. The big platforms have so much software on them that even the wealthiest company couldn’t buy it all even if they wanted to. I don’t know what a cannabilistic cash flow is. This may be a term of art I am just unfamiliar with. But if it means a cash flow built on the back of the host platform, this surely refers to the cash flow of all apps built on a platform. So I am unclear this idea moves the ball forward. If on the other hand the idea is that it will cost the host money for no clear ROI then this is indeed always possible, but just as obviously if there is no clear monetization strategy the dev is taking a huge risk. It can work out but of course most times, not surprisingly, it doesn't. (Clay Christen makes much of this dynamic and the challenges of marginal rather than absolute costing when he discusses such cases as Blockbuster competing with Netflix. But the undiscussed part of his argument is the hindsight effect. Blockbuster were right to ignore most of the market entrants. Most never got any traction. With a thousand flowers trying to bloom, which one will see the sunlight?) So building software that doesn't seem to make financial sense will doubtless reduce the risk of the platform company competing, but you'd better have something up your sleeve. The Instagram example is indeed important. But it is important precisely because of the very different behavior of Apple and Facebook vis a vis their devs. Apple has had long experience of working with devs and a deeply wired understanding of how to foster and manage relations with their developers. iOS is a platform. Apple provides some core apps but other than that it is a free range and the overwhelming majority of devs can be confident Apple isn’t going to compete with them. It seems to me that the whole point of DCs argument is that Facebook declared itself a platform, provided APIs, provided assurances that his product was seen as valuable and would be welcomed and then, having given him the confidence to build it, turned on him threatened to cut off his access to the platform on which his app relied and then offered to buy him out. This is very different behavior.
So to be honest, I don’t find the argument very clear. I’m not sure we agree on what the responsibilities of a company that declares itself to be offering a platform are. I can’t extract a convincing strategy here for how you feel devs can best to develop on a platform. And whilst you seem to feel you have some sort of lesson for DC about how to work on a platform even if the company baits and switches, I can't fathom what that lesson is.
What a depressing statement. Doubtless true but what a revealing and totally awful thing to take for granted. So now we live in a world in which not only are corporations people (thank you Judge Roberts) but they are psychopaths with no social conscience and we all take that pathology for granted. Enjoy the next century. :)
If FB did not declare itself a platform...if it had not encouraged others to build on its platform...if it had not encouraged DC to build his product on this platform...then you would be right. But if you are a platform, if you do encourage others to build on your platform (which is the whole point) and if you encourage a company to continue developing a product then it is not right. It may be realpolitik. It may be that having done all those things the platform company realizes that something it has encouraged is more strategic than it had realized, that it doesn't want a third party owning that product and it has to reel back its promises (which is what is sounds like here) but that is (a) a crippling result for the poor developer who took you at your word, and (b) and blow to your credibility as a platform. One incident like this won't kill you. Two won't. But at some point people just won't develop on your platform because there's no trust. ALL successful platforms have to walk this tightrope. Some do it better than others.
Representing yourself as a platform is something very different.
A platform a representation that you are providing a set of services on which others can safely build. It is a form of contract. And this representation has to be trusted because who in their right minds would otherwise invest on a 'platform' that turns out to be a flag of convenience? If a company loses this trust they ultimately lose the right to be called a platform. They lose developers and are ultimately left with a bunch of unused APIs.
Incidents like these described by DC are extremely important and should be publicly voiced because they bear directly upon the decision making of others who may be in the process of weighing their options. Should they or shouldn't they trust this alleged 'platform.' It is a huge strategic decision that can make or break a company. So people like DC who are prepare to go public with his experience are doing us all a favor because they are providing more perfect information, without which the market cannot operate accurately.
People can choose to criticize this or that dimension of the way various people played their parts, but that really isn't the key point, is it? Surely the key point is, can you trust the 'platformness' of FB? Did they imply one thing - that he was building a valuable product that they would be supporting - THEN choose to compete and wipe him out? That's the key point. The manners, the exact detail of how the wipeout was conducted aren't the point. If the story is accurate it is surely the breach of faith the is important. Some may argue that to expect otherwise is naive. But without some such faith there is no platform. You can't have your cake and eat it.