We use cookies to personalize content, to provide social media features and to analyze our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. For information on how to change your cookie settings, please see our Privacy policy. Otherwise, if you agree to our use of cookies, please continue to use our website.

In Software, The Interface Is The Product

37signals had an interesting post last month describing their development process, "interface-first design." From their book Getting Real (emphasis mine)
Too many apps start with a program-first mentality. That's a bad idea. Programming is the heaviest component of building an app, meaning it's the most expensive and hardest to change. Instead, start by designing first. Design is relatively light. A paper sketch is cheap and easy to change. html designs are still relatively simple to modify (or throw out). That's not true of programming. Designing first keeps you flexible. Programming first fences you in and sets you up for additional costs. Another reason to design first is that the interface is your product. What people see is what you're selling. If you just slap an interface on at the end, the gaps will show. --37Signals
A breath of fresh air! Too many online retailers lack agility in their IT, despite having great smart committed developers. Why is that? How much blame should be placed on their development methodology? waterfall development
Join the Discussion