26 karma · joined June 16, 2012
Also a 3rd party app.net developer active in the app.net community.
App.net is for the general consumer that's not going to be able to run their own server stack. If you can run your own server stack, you can use all these open standards outlined in this blog posts to consume the data and do what you like.
There's even a http://dev-lite.jonathonduerig.com/ so you don't need to pay anything to tinker with their API.
One could also argue that less data means less noise and more signal. Also the data on app.net is more structured (see their annotation implementation).
Let's do it right and then fix NAT
I think you spend time weighing each design because you're unclear on your final vision of your product. You haven't definitely answered what your values and needs are that you're trying to solve.
This may be a hard question to answer. This is why MVP are neat, you can get a product out to consumers quickly and use their response to develop values and a overall direction.
I find you if you think too far ahead, you don't leave any room for random disruptive opportunities that can occur in each step.
So know where you're going. Figure out and focus on the next step that gets you close to that.
Software Engineering is serious business, there's bugs, new features, maintenance, testing, etc. They failed to manage their code. You need to be realistic that with a team of 2-5 people it could take years to fix.
It might be best to put it out of its misery if they can't hold off their clients demands and buy you the time needed to rebuild it.