3 ms·
The problem with 3rd party apps is that the participation will always be a subset of the overall user base of App.net. The overall user base of App.net is cons
by jyap 14y ago
The problem with 3rd party apps is that the participation will always be a subset of the overall user base of App.net.
The overall user base of App.net is constrained by financial limitations (pay to play yearly).
So if someone creates an app off of their platform, like the simple chess app, they also need to be a member of App.net to play it. So while you may see the benefits and be a member of App.net, if you want to convince your friend to play who isn't a member of App.net you also need to convince them to pay and join App.net.
App.net is arguing that their business model does not require lots of users to be sustainable. While that may be true, for network effects to take hold, you need users.
- diego 14y agoThat is not true. You can create apps on top of app.net that can be used by non-members (as long as you respect their TOS). For example, you can see my cloud of what people talk about there: http://adn.loqix.com/ http://adn.loqix.com/ I could use my developer credentials to allow people to exchange information via the app.net backend. Of course I'd be responsible for whatever gets posted, so that places obvious limits on the kinds of apps I could write.
- jyap 14y agoYou can create apps on top of app.net that can be used by non-members Truth be told, that's not what they had in mind. No offense, all you're doing is data crunching. "3rd party apps" are all about user interaction. This then drives engagement, new users and in turn makes App.net valuable. But then again, best of luck to you if you can get money out of their developer incentive program by data crunching their own data set.