Write clear, user-friendly 'What's New' release notes for iOS and Android.
0 / 10 completed
1 / 10
Which phrase is the most user-centric way to open release notes?
User-centric release notes focus on user benefits ('You can now...') rather than internal identifiers or technical details.
2 / 10
What does 'under the hood' mean in release notes?
'Under the hood' refers to internal technical improvements (performance, stability, infrastructure) that users benefit from but cannot see directly.
3 / 10
Which is the better phrasing for a bug fix in release notes?
Release notes should describe bug fixes in plain language focused on the user's experience ('crash when signing in') rather than technical implementation details.
4 / 10
What is the recommended maximum length for iOS 'What's New' release notes?
iOS 'What's New' release notes allow up to 4,000 characters. While there is a technical limit, Apple recommends keeping notes concise and scannable.
5 / 10
Which release note format is clearest for multiple changes?
Bullet points grouped by category (New, Fixed, Improved) make release notes easier to scan and understand at a glance.
6 / 10
Alex from the mobile team just posted this Slack message: 'We've rolled out a new feature that allows users to upload profile pictures directly from their camera roll. It's pretty exciting!'. Which of the following best describes the tone and focus of this release note update?
This Slack message prioritizes a user-centric perspective. The focus is on *how* the new feature benefits the user (easier profile picture management) rather than the technical details. Options A, C, and D are overly formal and miss the core purpose of release notes: to communicate value to stakeholders. The phrase 'pretty exciting!' further reinforces this informal, user-focused tone.
7 / 10
Sarah is writing a pull request description for a new update to the iOS app. She includes the line: 'Optimized network requests for improved performance.' What does 'optimized' most likely mean in this context?
'Optimized' in this scenario refers to making something more efficient – specifically, reducing network traffic. The goal of optimization is almost always to improve performance by minimizing data transfer. Options A, C, and D represent entirely different changes that wouldn't be described as 'optimization'. It's a key term relating to backend efficiency.
8 / 10
You are reviewing a pull request for a new version of your app. The PR description states: 'Fixed an issue where users were occasionally experiencing crashes when accessing the shopping cart.' Which phrasing is MOST appropriate to use in your feedback?
Option A provides the most concise and user-friendly summary of the change. It clearly states the impact (critical bug) and how it resolves the issue. While options B, C, and D are technically accurate descriptions, they're overly detailed and less immediately understandable for a quick review. Focusing on the *impact* is key to effective release notes.
9 / 10
The 'What's New' section of your iOS app release notes needs to be kept under 300 characters. You need to describe a change that involves adding support for dark mode. Which of the following is the MOST effective phrasing?
Option A is the most concise and immediately understandable description of adding dark mode support. It's short, punchy, and clearly communicates the new feature to users. Options B, C, and D are too technical and lengthy for a 'What's New' section, which should be geared towards quick comprehension.
10 / 10
David is creating release notes for a major update to your mobile app. He wants to clearly communicate the scope of changes. Which format would be MOST effective?
A bulleted list is the most effective format for communicating multiple changes clearly and concisely. Each item can be easily understood, and users can quickly grasp the scope of the update. Options A, C, and D are too lengthy or technically complex for typical release notes, which should prioritize clarity and accessibility for a broad audience.
What will I practise in "App Store Release Notes — Writing Vocabulary"?
This module focuses on Mobile App Publishing — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Mobile App Publishing exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around mobile app publishing — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Mobile App Publishing exercises?
See the Mobile App Publishing hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.