“What’s New” in Your App Listing: How to Write Release Notes People Actually Read

Content
After publishing a new version of an app or game in RuStore, developers need to fill out the “What’s New” section. In practice, many treat it as a formality: they leave it blank, stick to the generic “bug fixes and performance improvements,” or use the space for moderation comments and technical notes.
While this section has little impact on app store rankings, it plays a direct role in how users perceive your product. It’s an important communication touchpoint where you can demonstrate that your app is actively evolving, explain the value of an update, and highlight the most important changes.
In this article, we’ll look at how to write effective “What’s New” notes that are useful for users, comply with moderation requirements, and help keep your app listing fresh and up to date.
Why This Section Matters
For users, the “What’s New” section is a quick way to see what has changed in the latest version of an app, discover new features, or find out whether a familiar issue has been fixed. That’s why clear and specific descriptions work far better than an empty section or a vague statement like “bug fixes and stability improvements.”
If developers publish the same generic release notes version after version, users gradually become frustrated. People want to learn about new features and improvements directly from the app listing, rather than searching through news posts, social media updates, or updating the app without knowing what has changed.
Common Mistakes
Leaving the Section Blank
The most common mistake is not filling out the “What’s New” section at all. As a result, users have no idea what has changed or why they should install the latest version.
aThis is especially common among smaller apps and games that release updates frequently but have little communication with their audience. The most common mistake is not filling out the "What’s New" section at all. As a result, users have no idea what has changed or why they should install the latest version.
Technical Notes and Irrelevant Content
Some developers use the section for purposes it wasn’t intended for, such as moderation comments, internal notes, or random text like “Everything’s great” or “Not sure what to write.”
These kinds of descriptions do not help users understand what has changed and will not pass moderation.
Moderation will also reject:
- meaningless or irrelevant text;
- internal technical references such as “fixed bug #21134”;
- mentions of prohibited resources or tools designed to bypass restrictions;
- links unrelated to the update description.
The only exception is links to developer-owned resources that provide a detailed overview of changes included in the new version.
Outdated Release Notes from a Previous Version
Another common mistake is forgetting to update the description before publishing a new release. As a result, the app listing may contain outdated information, such as references to expired promotions, old features, or events that are no longer relevant.
If the text clearly does not match the current release—for example, if a summer update is still promoting “New Year discounts”—moderators may replace the section with a generic description and ask the developer to provide accurate release notes in a future update.
To users, this looks unprofessional and can create the impression that the product is no longer actively maintained.
How to Present Changes in a New Release
The most important rule is simple: write for users, not for the release process. A good “What’s New” section is usually concise, specific, and written in plain language. You don’t need to publish a full changelog with dozens of items. What matters most is highlighting the changes users will actually notice.
A statement like “The app is now faster and more reliable than ever” says very little about the update itself. Specific descriptions are much more effective:
- Fixed a crash on Android 12 that occurred when launching the app.
- Improved catalog loading speed.
- Added the ability to undo task deletion.
- Redesigned the profile screen and navigation experience.
These descriptions feel more informative and meaningful to users.
Users also respond particularly well to updates that show the developer is listening to feedback. For example, highlighting a feature that users have been requesting for a long time often generates positive reactions and appreciative reviews.
Key Takeaways
The “What’s New” section in your app or game listing is a simple way to explain what has changed after an update and why users should install the latest version.
Even a short but informative description is more effective than leaving the section blank or relying on a generic “bug fixes and stability improvements” message. It can also help reduce repetitive post-release questions and prevent issues during moderation.



