Lesson #1 - Review scores are useless for optimising an app

While your apps review score provides a good overall measurement of the customer experience, it cannot tell you anything about an individual feature. Why you may ask? Most reviewers consider more than a single feature, journey, or attribute when giving their score. Therefore, a high or low review score cannot be directly attributed to any one part of your app.

Ipiphany uses AI to read each app review and record if the reviewer mentioned a problem or benefit relating to a specific feature. This breakthrough enables a direct measure of the quality of each individual feature.

Find the biggest problems in your app

Lesson #2 - Problems are only half the story

"Just tell me what my biggest problems are." is the most common request we see. The trap that people fall into when trying to answer this is to simply focus on the negatives. Many features that are complained about the most are often equally loved by customers for the benefits they provide.

To correctly prioritise improvements, you should look at both the problems and the benefits reported against them. The best way to do this in Ipiphany is by using the Net Opinion metric. Net Opinion combines problem and benefit percentages to uncover the features that show a strong problem or benefit bias. This can quickly tell you what are the best and worst performing areas of your app.

Correctly prioritise app feature improvements

Lesson #3 - You don't need to be the best in any one feature to have the best app

It is often a more efficient strategy to get your app performing relatively well across the board than to excel in any one area. Development resources can easily be wasted in trying to have the top feature in the category when coming in second or third would have virtually no impact on your app rating.

Always factor in how your features benchmark to ensure you are being as efficient as possible.

Correctly prioritise app feature improvements

Did this answer your question?