Hi, do you think user guide inside the app it is useful to avoid bad review? Do users read it before to leave bad review?
It happens to me people says in review: "it is not working description it is fake and so on..." I suppose they did not understand how it works by only reading description in app store.
Yeah user guide won't usually help unfortunately, unless it is forced in front them before they can use the feature.
Just take the review as constructive criticism and try to make the use of that feature easier to figure out. Try to get some outside opinions from people that don't have iPhones and are not familiar with the app. That way you can try to pinpoint what is being misunderstood in your app.
Hi, do you think user guide inside the app it is useful to avoid bad review? Do users read it before to leave bad review?
It happens to me people says in review: "it is not working description it is fake and so on..." I suppose they did not understand how it works by only reading description in app store.
Most of us developers face this problem that users don't even read the user guide and when the app don't work they blame it on us. Which really have bad effect on our reviews.
Many users don't read all of the app description either. It's really a challenge to take on. Games have the advantage that they can make tutorial levels. Apparently a lot of people liked the users guide added to iMovie, so there's one example to look at. I'm contemplating adding an interactive walkthrough to my app, but it's a good amount of work.
Paying customers generally leave higher ratings better reviews. Free customers have a tendency to leave bad reviews. If your app is paid and getting lots of negative reviews, I'd be worried. If you are getting negative reviews on a free app/version, don't sweat it too much. It won't effect free downloads too much anyways- people will just try all the similar free apps. Just make yours better than the other free apps similar to yours and they will use yours and/or buy your paid version.
Most of us developers face this problem that users don't even read the user guide and when the app don't work they blame it on us. Which really have bad effect on our reviews.
And some of us developers have the same problem too. Some questions on this forum are the result of not reading the documents.
For example in my app users don't understand how to trigger a specific functionality i described inside App Store description.
Should i put an explaining screenshot?
For example in my app users don't understand how to trigger a specific functionality i described inside App Store description.
Should i put an explaining screenshot?
You really need some sort of tutorial inside your app. The only reason I didn't straight up delete it right away, was because I had promised to review it. And finally sort of figured out how to use it (and I did read the description).
My suggestion would be to get one of your non tech savvy friends and tell him to use the app. Don't say anything, don't show him the description either (no one reads that). Just watch what happens, I guarantee you'll be surprised at how they fail to use it. Even the most basic stuff needs to be explained.
In my game, where it should be completely obvious what you are supposed to do, still a lot of people miss it. I have added a how to play screen, but still it's not enough and I'm looking for ways to make it even more obvious when people first start out (though they can figure it out pretty easily after a few times, which unfortunately it's not the case for your app).
For example in my app users don't understand how to trigger a specific functionality i described inside App Store description.
Should i put an explaining screenshot?
If it isn't obvious to the user how to use that functionality, I would suggest rethinking your implementation. Poor user experiences is always the fault of the developer, not of the user and forcing them to read documentation to figure it out will not help the situation. This is true even if you think it painfully obvious how the feature should be used.
I had this happen to my app recently: a very common user interface design for adding a new item to a table and a well-known user seemed confused by it. It was particularly eye opening for me because it was caught on video. I talk about it a bit here:
User guide to avoid bad review?
Both Apps FREE for a Limited Time! 
Linear Mode
