Start from hearing from real people who use similar apps.

Some items to pay attention to.

What do they think when they use these apps.

What are their priorities and tasks they need to accomplish

What do they love about the app

What do they hate about it

Once you have collected the above from a couple of folks you now have what is called User Research Data.

This data is important in a number of ways. It gives you a frame of context through which to view the project. This frame should align with the future users of your product so it’s key to find the right individuals to interview that align with the product you are building.

Users fall asleep to features

The best apps are many times the most simple. The funny thing about that is that people in the app development industry often think of simple as easy or less powerful. Both are fallacies. It takes a ton of time to pop off the barnacles of needless feature creep and curate a experience for a user.

Benefits are different than features

Ways we can promote powerful simplicity

Ask yourself if I removed this feature would a loose a core benefit?

What percentage of our user base would care and do they matter to the success of the project?

Would this feature be better hidden?

Should this feature be grouped with others for better flow or context?

Stripping away the non-essential is the extra step most software is missing.

Make a list ordered by priority. This will allow the most used and important things to be given more of a call out. This items should be high and prominent in the interface.

Draw out tons of sketches. This method allows a low time cost to feeling out ideas and seeing if they are worth pursuing.

6 votes, average: 4.50 out of 56 votes, average: 4.50 out of 56 votes, average: 4.50 out of 56 votes, average: 4.50 out of 56 votes, average: 4.50 out of 5 (6 votes, average: 4.50 out of 5)
You need to be a registered member to rate this.
(661 total tokens earned)
Loading...

Responses