This. I don't think App.net would have worked a year ago, maybe even not six months ago. But now, with Twitter actively attacking their developers, I imagine we'll be seeing a ton of ports from Twitter to App.net.
Twitter definitely considered the risk of cutting off their development community, but I don't think they intended to hand those developers off to a competing platform. Good timing from App.net.
App.net will get lots of hackers and people in our community, but in terms of reaching critical mass ... I don't think it will work.
People join twitter now out of societal pressure. "What is this thing? What is this ad on the subway that says I should follow them on twitter? Who's this athlete that is now Kobe Bryant with a strange @username at the end of his name?"
Developers, techy individuals, and people who consume twitter at a high level are more inclined to pay for it.
People who casually use it to help trend the latest hashtag about #whatmenreallywantfromawoman could care less. They're not going to pay a yearly fee for this, especially when the line between this and twitter is very blurry.
p.s. I am an app.net user and own a copy of netbot.
Sort of. The perception is that app.net is going up against Twitter. In your comparison, that's like saying that John Deere can outsell Ford.
However, the more realistic view is that app.net will remain a niche service, but one that suits techies very well. So, yes, John Deere will corner the market in tractors, but never branch out to cars.
Your perception and inference are both wrong. App.net isn't just going up against twitter, but rather the entire social networking paradigm where I have multiple signups and not enough use. If we use app.net to login to most major services and post, like I have to do with twitter, facebook and linkedin right now, I get away with a single login.
What'll drive adoption? The developer incentive program. This also answers your John Deere example... There will be a lot of offsprings from App.net. In a rudimentary tone - a fb-clone, an instagram clone, comments systems (bit.ly/qbdebut)etc...
I talked about Twitter specifically because the OP talked about Twitter specifically.
I don't doubt that there will be lots of offsprings from app.net, I'm just dubious about whether they'll gain any traction. "You only have to use one username/password!" isn't enough to get people to spend $5 a month.
I don't think that app.net is selling an identity service that will take off or be worthwhile, but I strenuously disagree with the assertion that people won't pay for single sign in on the Internet.
It is, in my opinion, the number one pain point on the web today. It affects users of all technical levels and the more you have invested in the web the worse it gets.
Ah, single sign-in... also offered by Twitter, Facebook, Google, Firefox, my email address...
I don't disagree that people might pay for it, but why would it by App.net I'd pay? Why would they even pay though? You can trust the App.net developers? No more than those listed, realistically.
The crux is how you define "critical mass". Dalton originally defined it as 10k users. He basically said that with 10k users you can have an interesting Twitter-like service.
Others are quick to point out that it will never reach Twitter-scale. There will never be a point where 90% or probably even 50% of the people you think matter on Twitter today are on ADN.
It's pretty clearly destined to be somewhere in between, and the question becomes what utility can you get out of that? Obviously the breadth of Twitter's firehose data is off the table, but you also have a lot higher signal to noise ratio, the benefits of a smaller community, and a practical means to fend off the Eternal September.
Can ADN be useful without ubiquity? I'm hoping to test the theory that finding the right 200 people to follow on ADN will give me everything I got from Twitter and more, even if they are not the 200 most interesting people on Twitter.
I think the App.net guys made an astute observation that the biggest hurdle to attracting developers was doing away with the perception as the platform as a gamble for developers.
It doesn't hurt that the Tapbots guys used the Tweetbot apps to piggyback on, of course.
Unlikely (read: impossible). Even if they could have ported it in the 6 days since that announcement, there's no way they rammed a new app through App Store approval that fast. They'd probably already have had to have submitted it before the announcement given current wait times.
The reward program was announced a week before Netbot was released (that is, today). Doesn't seem like the reward program was around when they decided to port over Tweetbot.
Just because it's money? You're also spending your time, effort, attention, and opportunity cost.
Is college meta because you spend money to work for free with people who also spend money, while learning from people who get paid money to teach you?
You're probably more used to services that monetize with ads, and encourage quantity of accounts at the expense of quality because it's good for their numbers. Nothing meta about one or the other.
I'm curious as to why they created a completely separate app. Why not just integrate App.net functionality into Tweetbot? I'd certainly be much more likely to use it that way... and I even paid the $100 developer fee for app.net.
Yeah they're essentially identical platforms in terms of interaction. Reading a stream, replying, retweeting/reposting etc...
They already have multi-user support, I'd rather interact with one app in this way. Or better, have the client merge your two accounts so that app.net/twitter become seamless and instead of thinking about who is on where, you simply enjoy it through the window of your client and none of that matters.
But.. I'm sure it took some good work to develop this and by simply updating Tweetbot they might not get reimbursed for that dev time. Rather, the new app must've been required.
I look forward to an integrated client down the road.
This looks awesome! I was wondering how long it would take for companies with Twitter clients to port over to App.net. The App.net platform looks like it may give Twitter a run for its money.
My favorite client in the new frame... I wonder how much time did take to port the network code to App.net? And if using a different key for crossposting.
I'm an AppNet user, but pretty limited in frequency. The primary reason is that I want proper posts to facebook and don't want to post in two places. I would like to see apps like this have the option to cross-post to facebook and twitter.
Ifttt fails because it does not allow proper link posts to facebook, and going through twitter to facebook results in truncated messages.
They have committed to supporting open standards like Activity Streams, PubSubHubBub, and Webfinger. While not OStatus explicitly, it looks like the majority of OStatus will be supported.
Twitter definitely considered the risk of cutting off their development community, but I don't think they intended to hand those developers off to a competing platform. Good timing from App.net.