|
|
|
|
|
by TomAnthony
4814 days ago
|
|
I didn't realise until this article that Alpha != App.net. Now that I do, a couple of problems spring to mind: * For startups, user acquisition often remains the biggest hurdle to success. Here they have to sting the user for a monthly subscription even to try the app. Asking people to open their wallets is going to massively reduce the people a startup get through the doors. * There are billions of active users on Facebook. It is the de-facto platform for interaction for most people. Why does the user want to change? Saying "but now you won't be the product, the platform will be" won't make clear to most users what advantage their might be. They'll respond "so I have to pay to be connected to less friends?". * The two above problems are cyclical and exasperate one another. I like the idea, I just think there are a lot of problems that are going to get in its way. |
|
As an app creator, even in this situation, where the user gets a free ride in your app because she’s a first time App.net user, you’re asking a lot from the user. When user acquisition and retention is your bread and butter, placing a huge level of complexity at the signup step, explaining what the hell an App.net account is, it’s basically strangling the acquisition part, and you never, ever, want to do that.
Taking a step back, what problems are they solving anyway? Shorten time to market for app makers? Because social app plumbing is getting pretty cheap and easy to pull off at scale with IaaS. Besides ending up with something very limited. Using App.net to build your app must add value, either for the creator, or the user. I’m failing to see how it does either. Unless, maybe, if App.net login is an optional part of your app that could lover the already in-place pricing scheme for all users (failing to see when this would make sense, but it’s possibly I guess).
Conclusion: Ask yourself, what app in the past 5 years, could have been pulled off, logistically, using app.net plumbing?