Applications have a tendency to grow and evolve beyond their original specification, it’s natural. As you work to create an application that solves a single problem you begin to see additional problems and feature creep rears its ugly head. Essentially what it comes down to is features vs. quality.

The more features that make it into the app, the more complex it will inevitably become. Each feature distracts the user from solving the initial problem and thus, the more diluted the app’s purpose will become. Let me explain by using a fast-food analogy.

Features

marmarais.jpg

Marmaris is situated on a busy street in Belfast, catering for the punters who roll out of the surrounding bars and clubs in the early hours of the morning. Marmaris isn’t a chinese takeaway, nor is it an Indian, Italian or a European food outlet. Instead it serves everything you could imagine; pizza, kebabs, fish and chips, burgers and Indian cuisine. Here we have a perfect example of feature creep. Instead of catering for a niche market with a specialised menu and doing it well, the owners have decided to offer every kind of food imaginable and ultimately do it poorly.

The premises where Marmaris is situated has changed hands at least 3 times in the past 4 years, with each owner trying their hand at the offer-it-all menu. Will Marmaris stand the test of time? I doubt it.

Quality

boojum.jpg

A street over from Marmaris we can find Boojum, a mexican restaurant. Boojum sells burritos and tacos. That is it. They have chosen a different model to Marmaris by choosing to sell one type of food and do it well. Just look at their reviews on Lookaly.

Of course these two eateries are catering for somewhat different markets but there is a lesson to be learned. Ask a user or customer what they want and they’ll tell you they want variety, choice and features, but what they really want is a burrito.

You might also like these posts: