No one really wants to be interrupted, much less for something silly while they’re in the middle of doing a billion things. So, why do app ratings follow this pattern? And why don’t developers attempt to talk more with their customers?
In this article, we’ll investigate the various tactics of prompting for app reviews and ratings and how to make them better. We’ll also talk about how to ask users for feedback in a way that benefits everyone.
Getting feedback on your app is important. How else can people tell you that your app is doing well or poorly? I’ve seen some great ways to prompt for reviews, and a few apps get it right, but there’s still room for improvement.
Further Reading on SmashingMag:
- Keeping Your Android App Popular After Launch
- Lessons Learned From An App Graveyard
- Improving Reviews And Testimonials Using Science-Based Design
- How To Engage Customers In Your E-Commerce Website
The reason why app store reviews aren’t as effective as they could be is that they’re a one-way conversation, asking the user to say something positive to everyone else. There should be something better, something more conversational, especially when things aren’t going well.
Why Ratings And Reviews Are Important
Both Apple and Google put ratings right alongside an app’s icon and title, giving users a quick way to judge the app’s quality. People are unlikely to download an app that doesn’t have at least three stars, so developers are incentivized to get the best rating possible.
This system, while mostly effective, breaks down in a few places. For example, a ton of non-developers on beta operating systems might complain that a particular app doesn’t work on their device. You’ll also hear folks blame an app for something that isn’t its fault — for example, blaming an alarm app for not going off, even though the phone’s battery died. (I’ll let you Google around for silly app store reviews. They’re fun!)
Some tech pundits recommend giving one star if an app prompts you for a rating, which is a reaction to ratings being asked for the wrong reasons. Simply asking for a rating leaves a tremendous opportunity on the table, one where you get to engage with users. You could be asking what you could do better, or you could be helping them with their questions.
Why Reviews Don’t Work As Well As They Should
When the waiter at a restaurant asks me how my dinner is, without fail, they do it when I’ve just planted my face in the dish. Now I’ve got to grunt my approval like an animal. It’s awkward. (Incidentally, I haven’t experienced this outside of the US, so not everyone will have experienced this.) This is what it feels like when a user is asked for feedback. Don’t bother them when they’re in middle of something.
Think of how this plays out for your typical user. They’ve just opened your app — let’s say to tweet something — and are interrupted with, “Hey, could you rate my app, plz!” Guess what their reaction will be. They opened the app to complete a task, and now you’re interrupting them to give a rating. They’ve got a lot to do, and rating an app is at the bottom of the list.
on the right time to ask for feedback. Developers should find the right moment to ask, and that moment will be different for each app. Here’s what he says about Clear, a lovely little to-do app:
“Clear for iOS shows the ‘Rate app’ dialog after a few conditions have been met. First, the user must have been using the app for a few weeks. Secondly, Clear will only ask after the user has cleared the remaining tasks from a list. This is a great moment in the app; users are feeling good for having just cleared their to-do list and in most cases are just about to exit the app.”
To return to our example of tweeting, feedback should be requested only after the user has tweeted a few times. In a photo-editing app, it could be after the user has edited and saved a couple of photos. Whatever the app, the point is to ask at the right time and to time the interruption well.
Shifting From A Rating Module To A Feedback Module: A Win-Win For Everyone
You might have noticed that I use the word “feedback“ more than “rating” here. I do it because we need to fundamentally shift our perception of app ratings. Developers should engage with the user to learn about their experience, whether good or bad. If things are peachy, then asking them to leave a review seems reasonable. If not, find out why so that you can make things better for them.
How do you do that? Ask them to email you.
This tactic is especially useful with frustrated users. If you don’t attempt to talk to them, they’ll likely post a nasty review in the app store, which you can’t reply to. Not being able to reply to reviews publicly is a good thing, by the way — public disagreements can get awkward, and at least one party won’t come out of it looking good. Email gets past that and puts two humans in touch to talk through a problem.
Hearing from the user directly gives you a chance to understand their problem and often yields actionable feedback, which will be a helpful supplement to crash logs or when you want to find holes in the user experience.
How We Implemented This Idea
After thinking through how to solicit feedback, my company implemented its feedback module in a business news app named The Business Journals. Here’s how the idea originally worked:
- Three days after opening the app, the user would see a dialog box asking whether their experience is good or bad.
- If the feedback is positive, the user is asked to leave a review.
- If the feedback is negative, the user is asked to get in touch.
- Users can dismiss the dialog box if they are too busy.
We thought that waiting for three days was a good compromise, giving users a decent amount of time to try out the app and gather their thoughts. The decision to wait a certain number of days, rather than a certain number of launches, was dictated by our users’ habits. Some of them launch the app a few times a day for a few moments and so would have a difficult time getting a feel for the app after just a few launches.
When a user would write to us, our support team would reply to them to help with their problem. Some complained about our update to the design, but most had lost their password or had a legitimate problem that we wouldn’t have been able to identify on our own. Ultimately, these emails were directly responsible for our considerable improvements to the app, helping us to squash bugs and remove obstacles between users and their content. The app went from 1.5 to 4.5 stars.
In short, the ideal solution is to open a dialog box at the right time with a simple question and answer. Where and how you implement it will depend on the app.
We’re planning to improve ours even more by asking users only after they have shared an article, thus minimizing interruptions further.
Feedback Modules: A Dark Pattern?
Some would call this approach to app ratings a dark pattern because it directs positive feedback one way and negative feedback another. But it has more to do with how it’s implemented. It’s a tool, inherently neither good nor bad.
Sure, it could be used for evil and to silence all dissent. Just don a black helmet and cape, build a Death Star and force choke all bad reviews to death by forwarding them to a never-monitored inbox.
Or you could use the approach for good to gather meaningful feedback from real users, in turn helping them to solve their problems and improving your product.
Not to mention, no matter how many barriers you put up, if your app is doing something evil, users will find a way to share their unhappiness with the world.
Hopefully, this has shed some light on how to balance your need for feedback with your need for a high rating. It’s not just about how many stars you get, but about how well you communicate with users. Whatever your method, make sure it respects the user’s time and energy. I’ve had great results with this pattern and will continue iterating on it.
I’d love to hear how you make this work for your users and to answer any questions in the comments section.
- “The Right Way to Ask Users for iOS Permissions,” Brenden Mulligan, TechCrunch