We are just getting started
blog.app.net
blog.app.net
I'm pretty Internet savvy, have spent most of my life building large web sites, and outside of reading articles about app.net every once in awhile (which I forget and then end up with the half-informed summarized memory above) I really can't figure out WHY I should be using it as a user. I'm sure part of it is them just not having a AAA app yet that just does something awesome, but I do wish they'd work a bit on their homepage so that all of it was more clear at first look.
Just some non-specific advice from an Internet traveler. If it's tough for me to figure out, it's likely tough for someone with much less experience. Right now, all I understand are your core values (which of course I agree with) and have trouble seeing how I actually use the service.
Thanks ahead to the people I'm sure that will comment on this and explain it a bit better, my general point is that I should be able to figure it all out quickly on one page.
Good luck duders! It's a product I'm generally curious about but never have enough time to do serious investigating on.
I have friends who use App.net and love it, but I don't think I'll be jumping on board because I just haven't been convinced that I need it.
It feels very much like "insiders solving very specific problems for other insiders" ... maybe insider isn't the right word, but my sense is they were born from frustrations with changes in the way Twitter handled the ecosystem ... i.e. 3rd party clients. So they said ok, we're going to build our own system that isn't trying going to restrict 3rd party clients.
So I (think) I get what they are on the periphery, but I still don't get the core product.
I'm sure it's good though - or at least good in spirit. Would love to hear more.
Can someone do an 'explain app.net to me like i'm 5 and have never used the internet'...?
App.net allows app developers to use app.net platform for a fee. App developers can integrate their user's app.net logins/profiles/network/photos etc. just like they do on facebook platform. App developers can also create users in the app.net platform. Users never see any ad. They also have good privacy settings. It's like win-win for both end-users and app developers. The only catch being app developers pay a nominal fee.
Why don't developers and users get a share of the business? Didn't the developers take on the most risk a year ago? Seriously, it's about time backers of crowd-sourced projects start demanding something tangible instead of just forking over cash to every salesman to come knocking.
Anyway, eventually the investors - and the rest of the bandwagon which is sure to follow - are going to want a return on their investment, so we know how this API-feel-good story ends.
Any developer building on top of App.net expecting long-term stability is kidding themselves.
I am a little concerned that a centralized silo with a sustainable business model is still a centralized silo and I personally would prefer a personal cloud/indieweb approach instead, but App.net is hardly some kind of Ponzi scheme.
It might be just semantics, but the 'alpha' label suggests that it is generally an MVP that is probably really buggy and annoying to use.
You can imagine my surprise when I read this post and find out about all of the cool things that the app.net team have achieved in the last year.
Somewhere along the line I appear to have missed any marketing messages. That might be my fault with some stringent Gmail filters?
Anyway, well done on the hard works guys, but are you really still truly in alpha? Just change it already.
Edit: I've just realised that 'alpha' isn't the project status: http://support.app.net/customer/portal/articles/761034-what-...
That might be a common user mistake. I don;t think I'm the only one that might make this (wrong) conclusion.