News for hackers. Stuff that matters.
Re:App.net 3rd-party revshare proposal by jenius on Sunday July 22, 2012 @04:19PM (#4278378)
Sadly, this project is going to fail - it won't even be funded. I understand the concept behind it, but for me app.net is like socialism - in theory it's great but in reality it just won't work. App.net is not created based on what people think and how they act, but rather on frustration with being a 3rd party developer. Onboarding the developer community to this shouldn't be difficult, and has already worked. But that's not what's important - what's important is how it looks to some random person. Let's simulate.

---------------------------------------------

'Hey, you should try app.net'

'Oh yeah? What is it?'

'It's the same thing as twitter, except you have to pay $50 to get on it, and it's nowhere near as popular as twitter, yet. But it has no ads, and they don't screw over third party devs.'

'Sounds questionable to me. I don't care about 3rd party developers, and not having an occasional ad pop up in my stream is not worth $50 to me. Especially if twitter is way more popular and useful anyway.'

'Well, shit.'

---------------------------------------------

This is not going to take off with the support of the dev community alone - it needs to appeal to normal people. And right now, everything about it does not. The name, the website, the pitch, the fees - none of it makes any sense to anyone but a dev.

Re:App.net 3rd-party revshare proposal by dalton on Sunday July 22, 2012 @04:27PM (#4278402)
Twitter in its early days made zero sense to end-users, and it was only through the effort of third party developers that it went mainstream.

I am getting tired of arguing with people about this. We will just have to agree to disagree. I am willing to take the risk of failure because I saw this exact developer-centric approach work before.

UPDATE: Regarding the comments below, if you read my original announcement post, I made the point that this is architected by be financially sustainable on a critical mass, small user-base: http://daltoncaldwell.com/an-audacious-proposal

I cited this Paul Graham post discussing the strength of a core geeky userbase: http://paulgraham.com/ambitious.html

Let's say that someone followed PGs advice on that proposal. Wouldn't the same criticisms about not appealing to normies also apply?

Re:App.net 3rd-party revshare proposal by nl on Sunday July 22, 2012 @08:20PM (#4278962)
Twitter in its early days made zero sense to end-users, and it was only through the effort of third party developers that it went mainstream.

Umm. I was an early Twitter user (April 07 - almost exactly a year before @daltonc), and I've never used any third party apps (except for Brizzly for a short period).

I think you are dramatically overestimating the impact 3rd part developers had. Twitter went mainstream when Ev went on Oprah. 3rd party devs worked on Twitter (initally) to scratch their own itches and because other people liked their work, not to make money.

Re:App.net 3rd-party revshare proposal by enra on Sunday July 22, 2012 @04:58PM (#4278486)
I think the OP means that it's not something non-developers want/care. Even if twitter went mainstream with 3rd developers, it was still apparently something people wanted.

PG also advices is that you should make things people want, people as users who use the app. People don't care about the tech or how nice it's for developers. If you build something that people like to use, and have nice API terms, people will use it and developers will develop on top of it.

Probably the only reason why people would care is that the apps and the whole network would be better, but that's huge chicken&egg problem.

If you look at the state on Windows Phone platform, Microsoft is even paying to people to develop on it, but no-one still care's because there are no users.

Re:App.net 3rd-party revshare proposal by dalton on Sunday July 22, 2012 @05:01PM (#4278492)
Twitter devs are being systematically intimidated, acquired and shutdown. There are credible rumors that the most popular 3rd-party clients will be summarily de-activated soon. What are they supposed to do now?
Re:App.net 3rd-party revshare proposal by lazerwalker on Sunday July 22, 2012 @07:36PM (#4278871)
People will complain, and the vast majority of Twitter users will continue to use Twitter, albeit via first-party clients.

It sucks for third-party devs, and it sucks for us power Twitter users who like our third-party clients, but look at every time Facebook introduces major changes: people huff and puff about switching to something else (Google+, etc), but the status quo doesn't actually change because the value is in the relationships they've formed on the service, not the way they interface with the service.

Re:App.net 3rd-party revshare proposal by jenius on Sunday July 22, 2012 @04:37PM (#4278426)
I didn't mean to argue with you about this Dalton, just to offer my shot at a reason why it's not taking off like you wanted it to. I am in support of what you're doing and hope it's successful, on a personal note.

Twitter in the beginning: "Post what you are doing & see what people you like are doing in 140 characters or less." This is very tangible and makes plenty of sense to normal people, immediately.

This is just something to think about, hope you don't take it as an attack or an argument. I'm clearly not the only one who has this opinion - it might be worth mulling over humanizing the project even if just a little bit.

Re:App.net 3rd-party revshare proposal by benatkin on Sunday July 22, 2012 @05:02PM (#4278495)
> I am getting tired of arguing with people about this. We will just have to agree to disagree. I am willing to take the risk of failure because I saw this exact developer-centric approach work before.

I hope you didn't mean this, and it was just a reaction to being irritated. Because if you consistently are this defensive, you'll have a hard time engaging the third-party developers.

Re:App.net 3rd-party revshare proposal by dalton on Sunday July 22, 2012 @05:06PM (#4278507)
Rather than edit my earlier comment, which some would classify as sneaky, let me paraphrase what I am trying to say: "I get it, this may not work. I have repeatedly admitted this is a crazy plan. If http://join.app.net doesn't reach 100% and thus fails, then we can say we tried. In any event, we will have learned something and no money will actually have changed hands."
Re:App.net 3rd-party revshare proposal by MatthewPhillips on Sunday July 22, 2012 @05:38PM (#4278584)
As an aside, I'm thrilled that you are blogging about the process and hope you continue to do so. At the end of the road, whenever that might be, it would be amazing to go back and re-read everything as a post-mortem.
Re:App.net 3rd-party revshare proposal by benatkin on Sunday July 22, 2012 @05:15PM (#4278538)
Good, glad you didn't mean it the way I interpreted it (I could have interpreted it wrongly, too). I liked how you replied in earlier threads. Please save being defensive for rare occasions when it's worth the risk that people might think you aren't open to discussion. You may need to just skip replying to some comments.
Re:App.net 3rd-party revshare proposal by citricsquid on Sunday July 22, 2012 @04:40PM (#4278433)
> Twitter in its early days made zero sense to end-users, and it was only through the effort of third party developers that it went mainstream.

Sorry if you've explained it elsewhere (I've not been paying much attention) but can you cite/explain that claim? My experience might be different, but most of the "normal people" I know of that use Twitter use it through the apps for their mobile (eg: iPhone, Blackberry) and they use it because that's the device they use, not because the apps are incredible and make Twitter appealing, the Twitter network is appealing. Based on this wouldn't the correct argument be that making Twitter available to everyone easily is what caused Twitter's mainstream success?

I think you explained the problem yourself: At day 0 Twitter made no sense to users and Twitter had 0 barriers to entry, all you had to do was sign up! How can app.net get over that problem while charging $50? If I'm correct that ease of access/use is what made Twitter mainstream wouldn't that mean you're doing the exact opposite of what made Twitter successful?

I really love the idea and hope it succeeds, but I don't see how you can appeal to anyone outside of the tech circle when charging for access.

Re:App.net 3rd-party revshare proposal by tptacek on Sunday July 22, 2012 @06:21PM (#4278700)
Without implying that I endorse this idea, which I think will fail simply due to network effects, it's a tiresome argument that says App.net doesn't have value to end-users because end-users don't care about ads.

It's true, as the argument says, that end-users won't care enough about Twitter's ads over the next year or two to abandon the service for a competitor. The ads themselves are just not that big of a deal.

But the need to draw revenue from ads is causing Twitter to make decisions that harm third-party developers. End-users don't care about third-party developers, but they very well might care about applications; if alterna-Twitter enables applications that users care about, the plight of developers or insidiousness of ads won't have to matter, because it'll be the apps themselves that sell the service.

Re:App.net 3rd-party revshare proposal by kyro on Sunday July 22, 2012 @08:05PM (#4278932)
I think that works in theory, but you have to look at what will draw users to care about applications. If the network effects aren't there, there's no reason why a user would be drawn to using a given application if the underlying service just isn't worth it. Users have a high tolerance for bad design and I think not paying for a Twitter that displays ads is well within that range of tolerance with the current Twitter app offerings.

You'd have to not charge users to get the network effects to kick in, but at that point, you're just a more open Twitter clone and you'll have to scramble to find a revenue source eventually.

Re:App.net 3rd-party revshare proposal by dinkumthinkum on Monday July 23, 2012 @01:18AM (#4279646)
An argument being tiresome doesn't speak to it being wrong, though. One big issue I see here is that, what if Twitter stopped being mean to developers? Eek. What if they also make ads less obtrusive ... Game over?
Re:App.net 3rd-party revshare proposal by mbreese on Sunday July 22, 2012 @08:50PM (#4279047)
I think it will fail, simply because they are asking the wrong question. The answer to Twitter isn't a company that controls a messaging bus (which is what the proposal is looking like). The answer is a federated protocol that will let multiple servers talk to each other.

For an email analogy, they are creating a POP protocol, when they should be creating SMTP.

That way you would have multiple clients vying for supremacy, but each able to communicate with each other. This would help drive users, since each service could have different features.

But unfortunately, it's a bit hard to build a company around a protocol.

Re:App.net 3rd-party revshare proposal by jazzychad on Sunday July 22, 2012 @05:34PM (#4278576)
A friend recently asked me what it would take for me to go back to developing on Twitter. I said, "Finally release the 3rd-party rev-share program they were promising back in 2009." They will never do this now with their current heading, but it would make a lot of sense. If they are becoming a media/ad company, they need as much distribution as possible, so let the ads run free outside their own walls.

For Twitter this would make a ton of sense because the rev-share would be based on impressions of ads, clicks, etc. The method to determine the dev's cut is straightforward and a known system (a la AdSense).

For App.net, as you correctly pointed out, the definition of "rev-share based on usage" is insanely complicated and the maximum value per user per month is capped at $2.08 (in the 50/50 scenario).

If I create a premium app.net client, would I still want to charge for it (e.g. iphone app)... would I even be allowed to charge for it in accordance w/ app.net TOS?

The idea of no first-party apps competing for user revenue is the ultimate dream of a platform that enables a 3rd party dev ecosystem. Sadly, many such platforms that began with that promise ultimately went back on it, much to devs' dismay. Much care would need to be taken to stick to this decision over the long term if this is decided up front.

Aside: I'm peeved that Svbtle doesn't allow comments. All the feedback you get must be out-of-band, and it creates extra steps for the people that read your posts.

Re:App.net 3rd-party revshare proposal by kyro on Sunday July 22, 2012 @05:42PM (#4278597)
I can't help but feel that you're severely underestimating the network effects and momentum needed to make a service like this useful to someone. If Twitter had a price barrier, I doubt they'd have 5% of the user base that they do now. I get where you're coming from, but at the end of the day, the cost of scrolling through a Twitter/FB ad in my feed is far, far less than buying my way into a social network that at least 90% of my friends won't use because of the price alone.

Even if you get geeks on board as your early adopters, you're still going to miss out on the much larger non-geek demographic that make these social networks what they are, even to geeks. Remember, you're going for a social tool here, and so you'll need to make it easy for a person's entire social circle to join else it'll be rendered useless. If you're trying to position this as dev-centric alone and to foster a github-like community around dev topics, then I could see this working. But as a catch-all social network, I don't think this will take off.

I commend you for trying, of course. Definitely a lot gutsier than I am to take on such a bold endeavor.

Re:App.net 3rd-party revshare proposal by dinkumthinkum on Monday July 23, 2012 @01:25AM (#4279670)
I think I agree with you. The more I look at it, I just don't see it. When I first heard about it, I had this feeling I really wanted it to succeed but then I didn't know what really way. Then I found out it is like this Twitter alternative, but I don't like Twitter. I don't like the concept of Twitter, I don't like its effect on society, on language, on communication. So, whatever, but I don't know if I would like this. Nevertheless, it could be, if it worked, a good step in a particular direction for social networking. However, again, I agree, I don't see how it could work.

But you know, it might be good to have an example of someone actually trying this and failing, so we don't have to just hypothesize that it will fail?

Re:App.net 3rd-party revshare proposal by dalton on Sunday July 22, 2012 @04:25PM (#4278397)
Hi, if you would like to provide constructive feedback on this, please email me, or write a blogpost, or talk to us on github here: https://github.com/appdotnet/api-spec
Re:App.net 3rd-party revshare proposal by 54mf on Sunday July 22, 2012 @03:55PM (#4278332)
Now this is interesting. I've had an RSS reader/platform on the backburner for a while, and was considering a similar revshare concept. It seems like a really great idea, especially for a new platform. Nothing like direct financial incentive to attract third-party devs.
Re:App.net 3rd-party revshare proposal by the_unknown on Sunday July 22, 2012 @04:05PM (#4278348)
As an end-user of these services will I be able to identify which developers should receive my payment?

For instance if I run two apps that use their service - a game that I play every few days and a social aggregator that runs in the background all day long but that I generally I would like to define that the game is more "important" to me in terms of dollars than the app is. Perhaps the game is worth 90% of my payment and the app 5% and some random service that I tried and abandoned should get the other 5%

Re:App.net 3rd-party revshare proposal by dinkumthinkum on Monday July 23, 2012 @01:30AM (#4279684)
I think this would just complicate things greatly. I also don't really see much benefit for the end-user to making such distinctions.
Re:App.net 3rd-party revshare proposal by TheBiv on Sunday July 22, 2012 @04:08PM (#4278352)
So the proposal is that I make more money if I make the best stuff...I like it...I just think that you have to define what "best" means pretty early or else I, as a developer, will come up with my own definition of "best" and it will probably look similar to my usage statistics...
Re:App.net 3rd-party revshare proposal by MatthewPhillips on Sunday July 22, 2012 @04:14PM (#4278367)
I think this is a bad idea. It's hard enough to come up with a business plan that is successful for yourself, you can't possibly come up with one that will be successful for all 3rd parties as well. Central Planning is never a good idea. In this particular instance you've set it up so that having users use 3rd party clients/services takes money away from you, disincentivizing you from treating 3rd parties well.
Re:App.net 3rd-party revshare proposal by dalton on Sunday July 22, 2012 @04:31PM (#4278414)
If this works, the idea of having no first party clients is on the table. I am having an open discussion to figure this out. I just hope people are constructive.
Re:App.net 3rd-party revshare proposal by MatthewPhillips on Sunday July 22, 2012 @04:43PM (#4278439)
So, in this scenario every user will be using a 3rd party client. This complicates things for a couple of reasons:

1) App.net's income per user is now 50% of the subscription price. You have to make that work financially for you.

2) The 3rd party's income per user is less than 50%. The most profitable 3rd party is going to be the client, so you've created a situation where interesting uses of the API that don't require user interaction are less profitable.

I want your platform to be successful, but I don't think this will contribute to it. You're going to spend a lot of time policing 3rd parties' attempt at gaming the system, which means time your not spending making the platform better. This is a rabbit hole you don't want to fall into.

Re:App.net 3rd-party revshare proposal by dinkumthinkum on Monday July 23, 2012 @01:27AM (#4279673)
I think no first party client is incredibly confusing for people.
Re:App.net 3rd-party revshare proposal by melvinmt on Sunday July 22, 2012 @08:50PM (#4279049)
Eventually all those 3rd party developers want a bigger piece of the app.net revenue pie and that means they will resort to, yes, ads.
Re:App.net 3rd-party revshare proposal by peterwiese on Sunday July 22, 2012 @05:24PM (#4278557)
i think you should add a moral support button. because right now i wouldn't pledge you $50 but i generally like the idea and i might join if this really takes off (and seems to offer me some unique value that i won't get elsewhere for free). i think showing the number of people that think like me somewhere on your page might encourage more developers to pledge something.
Re:App.net 3rd-party revshare proposal by currywurst on Sunday July 22, 2012 @06:36PM (#4278741)
I agree! I can really imagine dalton's internal struggle now as he tries to validate the idea in the real world. But I'm more impressed at the way this experiment is set up.

@dalton: Maybe you should add the infamous "Kudos" button to the join.app.net site ;) !