In order to keep your app easy-to-use and not overflowing with features, you need first of all to decide on the exact features that you will NOT implement since it's a one way road. Once you add a feature you can't remove it without the risk of getting your customers annoyed.
To add or not to add? This question arises when you start facing issues like: decreasing number of downloads, decreasing number of actual users, app concept isn't well recognised, etc. At this stage you need to take critical decision. But how do you know which idea to pick out of the big pool?
To narrow down your choice, determine the features NOT to be added — classify them into following 3 groups: Core
— Essential features. It will never work without them.Important
— Features that make the app unique and valuable.Nice to have
— Features that would be nice to have.
First, make it only with core and important features, then make sure that the problem is really solved. The nice-to-have features are not critical ones, so they should be rejected straight away. 'Nice-to-have' means that it's okay not to have them at all at this point. If they are too many, it will be hard to determine whether the app solves the problem or not.
In order to understand the primary needs (a new functionality or the existing feature improvement) our team at Omega-R have developed its own approach for evaluation of the current functionality and of the further app enhancements. We will be happy to share it with you in the Part 2
of this Article which will follow up soon.
We're recognized as a top App Design & Development Company on DesignRush