Saturday, July 12, 2014

Android and iOS - The 'feature fallacy' - Part 2

Learning from examples of good and bad interfaces and feature sets

One option for a designer hell-bent on packing multiple features into a mobile app is to release these features incrementally. This is largely how many successful tech companies like Apple operate. The corporation is notorious for launching devices with extremely limited feature sets, then slowly adding features as it becomes clear how best to implement them. Apple also tend to observe how customers are using its hardware and software, then tailor updates accordingly. You should consider adopting the same process when designing your apps.

Smartphone app users are exceptionally critical – even if your app is free. So, you’ll have a better chance of getting good ratings for your app if you take things one step at a time. Try and do one thing, really, really well, rather than pack in two or more additional features. Bizarrely, Interface design analysts have observed how the addition of features often tends to infuriate the bulk of app users. The largest group of people using your app will be those using the least number of its features, design your app with these people in mind because they represent the mass market. The majority of smartphone users have very specific needs that are often overcomplicated by programmers.

The importance of elegance in app design

Many designers think that complex equals powerful. In reality, simple equals powerful. Do one thing the best you can before adding extra functionality. Don’t get distracted.

Here are a few examples of the apps we think best embody this design ethos.

Read Back Android and iOS - The 'feature fallacy' - Part 2

No comments: