Good day.
Everyone knows how to publish your application in the Marketplace. The process (fairly automated) has been described many times. But how to set the vector of development of the application next? Help us in this reviews.
Feedback
If your application is a large commercial project, then most likely there was a QA (testing) stage or at least a launch on the end device. Then, the GUI designer made the final touches and your application is available to the end user.
')
How can I leave a review:
- Through the browser (http://www.windowsphone.com)
- Via Zune
- Via smartphone based on Windows Phone 7
In all these cases, the user logs in with his account and leaves a review, which is the following:
- Review date
- Author
- Rating
- Headline
- Description
- Region (in Marketplace)
Each user of the application can leave one review for the current version of the application,
but can change it. Thus, you can get feedback on the application. It is also worth noting that reviews in different places of publication may be updated in different ways. Often there is a situation when there are reviews in the Dashboard (create.msdn.com), but they have not yet appeared on the site. This is due to the fact that the user left it through the phone.
Rating - a number from 1 to 10, which translates into a 5-star system. Therefore, you can see the rating in the Marketplace of this type:

This rating is generated on the application page and you can see that it has the name “ratingLarge fourPtFive”. It turned out by transferring the average rating (8.588 in this case) to asterisks and rounding. Step rating: half a star. This moment is a bit hidden, but I assume that this is exactly what is happening.
We now know the structure of the review. How to work with him?
Work with review
The most important element is the content of the review. Without considering the cases when the user made a mistake or was not guided by logic when making a review (a false review is always difficult to detect), there most likely contains either a description of the problem encountered by the person or an enthusiastic joyful response about the application. We will try to increase the number of the latter.
Review Description
When processing feedback to improve the application, I had some tips that could be useful to someone:
- Do not take everything too close to your heart. Focus on the problem - it is more useful.
- Come up with a solution that suits both you and the user.
- Do not enter into an argument in the reviews (very bad option)
- Have a clear vision of your application (not the development plans, but the main task)
- Don't change the app after one bad review.
I remember myself very worried when one angry review (almost offensive) appeared on the application page. There were a lot of emotions, but the desire to make the application better prevailed.
Write to the author
Now only the author's name (login) is available, but there is an application that will allow the author to write through the Zune message system. This application is
Windows Phone 7 AppReviews . Posted by: Tom Verhoeff. His
blog .
Key features:
- View reviews for all regions where your app is hosted.
- Export data to CSV
- View statistics
- View reviews
- The ability to write a review author
Click on the author and enter the message. The text of the message is limited. Be concise and do not forget to leave contact information. Then send a message. There are no confirmations, and for the region ru-RU it is written “Not available in your region”, but the message has been sent.
More tips
In the application's help or on one of the pages, add the ability to write to the author. This will simplify the process and do not need to wait for a possible answer. The user himself will be able to report an error.
It is convenient to compare Stacktrace with the revocation date, if it contains a technical error. If it is not processed, then you will see it.
I hope this information will help the developers.