Designed for Use, 2nd Edition

Chapter 28 Removing Features

The previous chapter was about avoiding feature creep—how to make sure you don’t overload your product, and your users, with too many features. But you might find yourself in situations where it’s not about refraining from adding unnecessary features anymore. What you really need to do is get rid of some of your existing features.

You might have reached this point for a number of reasons. Maybe your technology has become outdated. A decade ago it might have been absolutely reasonable to add FTP syncing to your application, but today there are better ways, and the FTP feature has become a liability. Perhaps you added ...