All posts tagged app.net

→ What Makes App.Net So Great

This list from Dalton Caldwell about all the ways that people can use App.net’s data just emphasizes how different of a service it is from Twitter. I wish more of my friends would shift over to it.

→ PourOver – App.net Syndication of your RSS Feed – now Available

The developers of App.net saw a need their users had, and they created an elegant solution to deal with it. That is pretty awesome.1


  1. Of course, I cannot imagine Twitter doing this. Bloggers who want to syndicate their RSS feeds are far, far from what Twitter wants for users at this point. 

→ Ben Brooks on the Difference Between Public Networks and Private Networks

Ben Brooks, after explaining the difference between public and private golf courses:

That’s the difference between Twitter and App.net to me. Twitter is the public golf course, the coach seat. It’s where everyone is, and that’s exactly the problem. App.net is where a few people that are invested in the product, its direction, and the overall health of the service, go to socialize online.

He makes a pretty spot-on comparison.

→ Matt Gemmell’s Explanation of App.Net

Matt Gemmell has put together a comprehensive explanation of everything App.Net. If you are on the fence about whether or not you want to give App.Net a try, I highly recommend reading Mr. Gemmell’s explanation.

→ Kiwi App.Net Client for Mac Now Available

Easily the best App.net available for the Mac.

→ App.Net Introduces a Free Tier

The little social network that could keeps improving. I hope this means an influx of new, quality users.

→ Riccardo Mori writing about his first Month on App.Net

But what really stands out, for me, is the atmosphere. So far, it’s probably what I like most of App.net. First of all there’s that different pace I was mentioning before. The feeling is of a quieter place than Twitter, and not only because it’s a much smaller place. People seem more relaxed, friendlier, more willing to engage in long conversations and more willing to include you if you join in a conversation long after it’s started. With Twitter, I think social network; with App.net, I think community. This is the core difference, in my opinion. Two main things drive people towards this behaviour, I believe: the paid membership model, intertwined with ‘the cause’. An App.net member may be a stranger to you, but you’re both on App.net because you both have decided to pay for a better online social experience and because — explicitly or not — you both agree to ‘the cause’, i.e. the set of core values on which the founders chose to build and develop App.net.

I agree completely.

Netbot Updated with Push Notifications

Netbot, the App.net client from Tapbots, has been updated to include push notifications. The iPhone1and iPad versions are both available now in the iOS App Store.


  1. Affiliate Link (as are all app links in this post.) 

→ A Directory of App.Net Applications

App.net seems to be really growing recently. If you haven’t taken the plunge yet, there is now a directory of clients to help you make some initial choices1.


  1. I have no strong preference for any of the various ac clients, but for iOS, I strongly recommend Netbot, available of iPhone and iPad. (Affiliate Links) 

Netbot for IOS Released (i.e. Tweetbot for App.net)

Tapbots has released a version of their Tweetbot Client for App.net, aptly named:Netbot. It comes in both iPhone1 and iPad versions. Though I have really been enjoying Felix as an iPhone App.net client, I think I am going switch over to Netbot.


  1. Affiliate Link (as are all app links in this post.) 

→ An iOS Client for App.net to Rival the Best Twitter Clients

Spoonbill1 is finally out of beta, and it is amazing. If you use App.net, you are going to want to pick this up.


  1. Affiliate Link (as is the main link on this post.) 

The State of App.net

There has been a lot of good writing recently about the current state of App.net. It seemed to start with Glenn Fleishman’s article:

Pipe Dream or Alternate Universe — App.net doesn’t need to get everyone to move away from Twitter. It only needs to get everyone you know to move. I’m being facetious, but it’s true. If you have even a relatively large group of people with whom you interact on Twitter, and they start turning their attention to App.net interaction, you may find yourself there as well. For now, I run Twitter and App.net clients side by side, since App.net is still in alpha, and only a small number of people I know are early adopters like myself.

Mr. Fleishman’s article is a comprehensive explanation of what App.net is in its current form and what it hopes to become. I recommend it to anyone who wants to get a better foundation to decide whether or not to sign up.

Building on Mr. Fleishman’s article is Federico Viticci’s write-up:

For my job, I talk to developers and creators on a daily basis. And right now, developers are picking up some good vibes from App.net. There’s a lot of experimentation going on, support from the company, and an overall feeling that, if this is will work, maybe a better (and different) Twitter could be possible. It’s too early to tell — after all, Twitter still works — but it’s a good start nevertheless.

I get the same impression from my developer friends that Mr. Viticci is getting from his developer contacts. The service is just starting and developers are trying to figure out what it will become. This early period of developer enthusiasm should be the story at the moment, not the statistics of who is doing the most posting.

→ Pocket Updated to add App.net Support

I hope this is a trend.

→ A Solid (though Early) App.net Client

Appetizer is my App.net client of choice. It is still in its early stages, but it handles the basic App.net functionality1 well.


  1. I also have tried Mention and moApp. Mention is just not my style, while I feel Appetizier handles things a little better than moApp. Also, the moApp developer was kind of offensive on App.net recently and that makes it hard for me to support him. 

→ The First App.Net Client in the App Store

The app probably will not blow people away, but there is some credit for being first.

→ App.Net Is More than Just Twitter with a Different Business Model

Watts Martin:

If we think Twitter the service has long-term value as a fundamental Internet service—and I do—then Twitter the company needs to be disrupted. That’s not going to happen by building a clone with a more liberal software license or a better business model. It’s only going to happen if such a service becomes Internet infrastructure, no matter how many business models that breaks along the way.

I think Mr. Martin is confusing the current alpha.app.net with app.net as a whole. App.net’s founder Dalton Caldwell has said that he does intend for App.net to be infrastructure. In fact, he said he did not want to put out the alpha originally because he was afraid that people would miss the point of what App.net is. I encourage Mr. Martin to listen to the first 30 minutes of this week’s This Week in Google, where Mr. Caldwell explains his actual vision for App.net. I think it is much more in line with what Mr. Martin wants than he realizes1.


  1. Kyle Baster has written a commentary building on Mr. Martin’s piece. His argument seems to be slightly different from Mr. Martin’s: he would prefer that Twitter’s replacement be some kind of “open standard” like RSS or IMAP since that will allow for everyone to use it. I would counter Mr. Baxter by saying that an open standard and its associated technological hurdles would be a barrier to entry similar to the existing App.net membership fee. In fact, the skill required to implement the open standard might be a higher barrier than the current fee structure. 

More Excellent Writing about Twitter’s API Changes

The announcement of Twitter API changes has led to another round of great analysis, including: Dermot Daly writing on the Tapadoo company blog telling people to at least wait until the dust settles around the Twitter ecosystem, Paul Haddad writing on the Tapbots Blog telling us that the sky isn’t falling, and that Tweetbot should be around for a long time, Lex Friedman at Macworld talking about the opportunities App.net has to take advantage of the changes, and Brett Terpsta on his site saying that App.net could be the replacement that people who use Twitter differently from the general public could move to.

I have a hard time remembering a topic that has resulted in so many quality, well-thought-out opinions.

UPDATE: Shawn Blanc posted his thoughts just as I was hitting send.

→ Excellent Information about App.net on this week’s This Week in Google

This week’s episode of This Week in Google starts off with 30 minutes or so of the panel talking with App.net’s Dalton Caldwell. The interview is very insightful as to App.net’s future. I was unaware of Mr. Caldwell’s vision that App.net would be infrastructure focused (i.e. they’ll be an “API company.”) In fact, he was torn about even producing the alpha.app.net website because he wanted third-party clients to handle that and he did not want people to think he was simply making a Twitter clone. The whole interview is quite good and definitely worth a listen if you are interested in App.net or the social web.

→ How App.net Can Change Everything

A lengthy breakdown of the potential value of App.net from Orian Marx, including benefits to users:

App.net is fundamentally driven by a desire to empower users and has the potential to establish a new standard of excellence in the treatment of user data and permissions which will be innate to the core platform upon which App.net developers will build. App.net has publicly declared that their most valuable asset is their users’ trust. (emphasis in original)

and developers:

App.net will combine the simplicity of cloud infrastructure with the power of web frameworks to deliver the best platform for developing social web applications. Social web apps are built around concepts like users, posts, connecting and sharing. App.net will provide a scalable infrastructure and a base model for these concepts upon which startups can innovate without reinventing the same wheels again and again. Developers will spend less time just trying to make their applications functional, so they can have more time to make them unique and useful. (emphasis in original)

Currently, App.net feels like Twitter did during its early stages, with people trying to figure out how to best structure the community around the infrastructure. It is clearly more evolved than Twitter though, as I do not see the various “I am doing X” posts that were so prevalent during Twitter’s early days. The main thing holding back App.net now is the lack of quality native desktop and mobile clients. I have a feeling those will start showing up before too long.

(via Dan Benjamin)

→ Notifications for App.Net in Mountain Lion

If you’re looking for a way to add notifications for App.net in Mountain Lion, this github project does the trick. I downloaded the code directly from there, however, there is a compiled version out now. I have not tested the compiled version, but the version from github works quite well.