3 ms·

I actually debated on including the word "social" in the title and ultimately decided against it. It doesn't matter if you're building productivity software (sp

I actually debated on including the word "social" in the title and ultimately decided against it. It doesn't matter if you're building productivity software (spreadsheets, databases, etc…) or social software, you're going to learn exponentially more about the pain points your users experience once your app is in the wild. At the end of the day users decide how they are going to use your product.

TillE 16y ago
I'm not a total devotee of Extreme Programming, but it does have a lot of good ideas, chief among them being doing frequent releases from the very start, and constantly getting feedback from the customer. In a context where your customer is the general public, it's fairly obvious how to adapt that development model. Anything from a limited closed beta to a simple public release might be appropriate, but ideally you want to develop in a way such that you have a minimally functional but stable app fairly quickly, and add features and refactor (hopefully based on user feedback) from there.