From Apple to Facebook to Twitter, are we learning that APIs and App Stores are simply traps wherein complements are commoditized so as to drive adoption and to explore (or ripoff) enhancements?
These things seem to be win/win/win for the providers and angst/angst/angst for wannabe collaborators.
Exactly, developers seem to flock to platforms like Apple, Facebook and Twitter based on the fact that they have a large and growing user base without giving thought to this issue of commoditization of complements and how it ultimately destroy the business or livelihood of these developers.
Most people building products or sharecropping on other people's platform never make meaningful income and yet those platform prefer to announce large sums paid out to developers to encourage you to keep building complements. Apple will claim they paid out $5 billion but when spread out or divided among the numerous app developers it becomes peanut and not enough to pay their bills. You won't hear Apple give you the breakdown as that will expose them and destroy the wrong picture they want to paint to developers. Neither will they tell you that to pay out $5bn they made atleast $2billion based on their 30% cut, off your work and yet countless app developers are not making enough to live on.
They don't tell you that iOS app success is a "lottery": 60% (or more) of developers don't break even
I really hope people will think hard before building their business on the back of Apple, Facebook, Twitter or any such platform. You can use them as as distribution without making your business model entirely dependent on them and that is the way to go.
Be your own bitch and not a Twitter, Apple or Facebook bitch:
While I hate to blindly agree and lump all these successful companies into API traps, you are pretty much right. From a business standpoint, if Facebook (or any other API company) sees massive growth/activity in an application on its platform, you better believe they are going to take notice and have some course of action.
The main aggravation/issue stems from developers wanting to use these APIs to gain access to users without fully qualifying the risks. I could easily be building a fantasy sports app on Facebook thinking, "they won't EVER get into this market. They have much bigger problems to solve." 2 years later, they get into the space and shut me down because I am a competitor.
These "wannabe collaborators" are not trying to improve the experience on said platform. They are trying to gain access to a vast database of users with low barriers of entry and an easy to use(/abuse) marketing channels. It's unfortunate that no one has the foresight into understanding where a company as large as Facebook/LinkedIn/etc may pivot into, but only insiders really have first hand knowledge of this sort of thing.
The rules on displaying a tweet on a website seem so batshit insane I can only assume that my interpretation of it is wrong, and it should only apply to applications that provide the functionality of a Twitter client.
I would use twitter web or the official apps if they clearly displayed the @username instead of the "real name". The latter is pretty much an useless field that only adds confusion.
I just hope that the new display guidelines don't enforce displaying the real name over the username.
Now I'm curious how Twitter will respond: some open souce developers are working on integrating Twitter posts to buddycloud. That means Tweets will be displayed in a buddycloud channel. How exactly does twitter expect someone running a twitter-buddycloud gateway on their domain. Additionally buddycloud channels (containing tweets) can be displayed in a text client ala https://github.com/Schnouki/bccc#screenshot Are we expected to <blockquote> our VTs? :)
My interpretation is that it's referring to actually embedding a tweet in a way that pulls it live via the API (or otherwise presented as a tweet entity), and that just quoting someone's tweet (like one would quote an article) is still fine (how could it not be?). I could be wrong.
These kinds of specific restrictions that aren't actually specific enough and really up to their whim are troubling. Twitter needs to be careful that their regulations don't become too much of a burden on their ecosystem. The vagueness and uncertainty of their rules is the problem.
Question: is there anything stopping an app from using an invisible embedded web view to pull content from Twitter, mimicking a plain browser, and then scraping the content from the DOM as a poor man's API?
It would be tedious as hell, especially now that Twitter is all-Ajax-all-the-time, and it would be a moving target as they made changes, but could Twitter really do anything to stop it?
I think the answer is no, they can't stop you. And perhaps I'm being naïve, but it doesn't seem like it would be too terribly tedious if you used a scraping library, at least not for replacing basic API functions (i.e. getting a user's recent tweets).
Obviously this would be limited to public tweets (no private tweets, no tweeting on the user's behalf, and no DMs).
> Question: is there anything stopping an app from using an invisible embedded web view to pull content from Twitter, mimicking a plain browser, and then scraping the content from the DOM as a poor man's API?
Yes, it's called iframe busting. You can't force a page into an iframe that doesn't want to be there.
The problem is the teeming masses that are the ones creating all those nonsensical tweets that make Twitter so popular couldn't care less about these problems ...
I find myself wondering: why the heck do I even have a twitter account? I hardly ever use it anyway. A political gesture is as good a reason as any to simplify my life.
Turns out I need it for authenticating a couple of external sites. But its days are numbered..
I can't understand how this affects companies like twitmusic.com which just closed a round from 500 startups. Or perhaps disqus.com which has a lot of integrations with twitter in their app.
What does rule 5a, "Tweets that are grouped together into a timeline should not be rendered with non-Twitter content. e.g. comments, updates from other networks," mean for Gwibber and other desktop social clients?
[+] [-] politician|13 years ago|reply
These things seem to be win/win/win for the providers and angst/angst/angst for wannabe collaborators.
[+] [-] throwa|13 years ago|reply
Most people building products or sharecropping on other people's platform never make meaningful income and yet those platform prefer to announce large sums paid out to developers to encourage you to keep building complements. Apple will claim they paid out $5 billion but when spread out or divided among the numerous app developers it becomes peanut and not enough to pay their bills. You won't hear Apple give you the breakdown as that will expose them and destroy the wrong picture they want to paint to developers. Neither will they tell you that to pay out $5bn they made atleast $2billion based on their 30% cut, off your work and yet countless app developers are not making enough to live on.
They don't tell you that iOS app success is a "lottery": 60% (or more) of developers don't break even
http://arstechnica.com/apple/2012/05/ios-app-success-is-a-lo...
http://andrewchen.co/2012/08/15/mobile-app-startups-are-fail...
I really hope people will think hard before building their business on the back of Apple, Facebook, Twitter or any such platform. You can use them as as distribution without making your business model entirely dependent on them and that is the way to go.
Be your own bitch and not a Twitter, Apple or Facebook bitch:
http://techcrunch.com/2011/05/23/fred-wilson-be-your-own-bit...
[+] [-] phereford|13 years ago|reply
You can even throw LinkedIn into this group (http://blog.programmableweb.com/2012/06/21/linkedin-shuts-do...).
The main aggravation/issue stems from developers wanting to use these APIs to gain access to users without fully qualifying the risks. I could easily be building a fantasy sports app on Facebook thinking, "they won't EVER get into this market. They have much bigger problems to solve." 2 years later, they get into the space and shut me down because I am a competitor.
These "wannabe collaborators" are not trying to improve the experience on said platform. They are trying to gain access to a vast database of users with low barriers of entry and an easy to use(/abuse) marketing channels. It's unfortunate that no one has the foresight into understanding where a company as large as Facebook/LinkedIn/etc may pivot into, but only insiders really have first hand knowledge of this sort of thing.
[+] [-] look_lookatme|13 years ago|reply
[+] [-] andy_herbert|13 years ago|reply
[+] [-] jmillikin|13 years ago|reply
[+] [-] MatthewPhillips|13 years ago|reply
[+] [-] mechanical_fish|13 years ago|reply
If you've got any widget that uses the API the Tweets are going to have to conform, it would seem.
[+] [-] darkstalker|13 years ago|reply
I just hope that the new display guidelines don't enforce displaying the real name over the username.
[+] [-] imaginator|13 years ago|reply
Now I'm curious how Twitter will respond: some open souce developers are working on integrating Twitter posts to buddycloud. That means Tweets will be displayed in a buddycloud channel. How exactly does twitter expect someone running a twitter-buddycloud gateway on their domain. Additionally buddycloud channels (containing tweets) can be displayed in a text client ala https://github.com/Schnouki/bccc#screenshot Are we expected to <blockquote> our VTs? :)
[+] [-] rhizome|13 years ago|reply
[+] [-] kylemaxwell|13 years ago|reply
[+] [-] alecperkins|13 years ago|reply
These kinds of specific restrictions that aren't actually specific enough and really up to their whim are troubling. Twitter needs to be careful that their regulations don't become too much of a burden on their ecosystem. The vagueness and uncertainty of their rules is the problem.
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] lukifer|13 years ago|reply
It would be tedious as hell, especially now that Twitter is all-Ajax-all-the-time, and it would be a moving target as they made changes, but could Twitter really do anything to stop it?
[+] [-] poblano|13 years ago|reply
I think the answer is no, they can't stop you. And perhaps I'm being naïve, but it doesn't seem like it would be too terribly tedious if you used a scraping library, at least not for replacing basic API functions (i.e. getting a user's recent tweets).
Obviously this would be limited to public tweets (no private tweets, no tweeting on the user's behalf, and no DMs).
[+] [-] MatthewPhillips|13 years ago|reply
Yes, it's called iframe busting. You can't force a page into an iframe that doesn't want to be there.
[+] [-] zdw|13 years ago|reply
I hardly ever use them, but things like Bitlbee or the ruby twitter gem are handy once in a while...
[+] [-] gcr|13 years ago|reply
[+] [-] cicloid|13 years ago|reply
[+] [-] dinkumthinkum|13 years ago|reply
[+] [-] ricardobeat|13 years ago|reply
[+] [-] notatoad|13 years ago|reply
Nobody is entitled to twitter's data except twitter.
[+] [-] revorad|13 years ago|reply
[+] [-] kunle|13 years ago|reply
[+] [-] akkartik|13 years ago|reply
Turns out I need it for authenticating a couple of external sites. But its days are numbered..
[+] [-] joewee|13 years ago|reply
Can someone shed some light on this?
[+] [-] Kerrick|13 years ago|reply
[+] [-] MatthewPhillips|13 years ago|reply
Twitter doesn't want to be abstracted away as just another stream of messages.
[+] [-] protomyth|13 years ago|reply
[+] [-] ojbyrne|13 years ago|reply