applicomhq
I think you need to walk the line on this one. That's what we do with Apollo... We managed to include a CRM in there, and still keep the UI very simple.
Tony Mobily http://www.apollohq.com
Adding features is hard work, risky, expensive, and sometimes counterproductive (!). It's hard work, because you need to change an existing, working piece of software with new code, and deploy it. Including possible database changes. It's risky. Deploying a new version of your software might introduce nasty bugs, huge usability problems, or you might change the way things worked before, actually displeasing a lot of users. It's expensive. Programmers aren't cheap. Then you need testing, QA, ticket triage... all things that cost a lot of time, and money. Counterproductive. Your new features might only benefit a tiny portion of your userbase, and might not attract new customers. They might break your existing model. And so on.
Once you've reached a good feature set, doing continuous development is more of a life choice, rather than a business decision that makes sense.
Really.
Tony Mobily http://www.apollohq.com
this approach was tried by Gnome's Nautilus for a while, a few years back... and it failed miserably. It feels to me like a bad excuse for not designing a good UI in the first place...
Tony Mobily http://www.apollohq.com
Tony Mobily http://www.apollohq.com