LogPulse

LogPulse / templates

Mobile app release notes without the guesswork

Tell users what changed and whether they need to update. Keep your public archive detailed, then adapt the wording to each app store's current metadata rules.

Example 1

Mobile feature release

New

Version [version]: [user-visible benefit]

Platforms: [iOS / Android] Availability: [release date and phased rollout details]

New

  • [Feature and where to find it.]

Improved

  • [Specific workflow improvement.]

Before you update

[Minimum supported OS, compatibility changes and any action required.]

Not seeing the update yet? [Explain the actual rollout schedule and support route.]

Why it works: Separate app version from OS requirements. Never promise instant availability during a phased store rollout. This web markdown may need plain-text adaptation for store listing fields.

Copy the markdown · replace illustrative details
## Version [version]: [user-visible benefit]

**Platforms:** [iOS / Android]
**Availability:** [release date and phased rollout details]

### New
- [Feature and where to find it.]

### Improved
- [Specific workflow improvement.]

### Before you update
[Minimum supported OS, compatibility changes and any action required.]

Not seeing the update yet? [Explain the actual rollout schedule and support route.]

Example 2

Mobile hotfix

Fixed

Version 3.4.1: a fix for offline drafts

This fictional example describes a patch for iOS and Android.

  • Drafts saved offline no longer disappear from the list after reconnecting.
  • The retry message now explains when a connection is needed.

Update from your device's app store when version 3.4.1 becomes available. Previously missing drafts are not automatically restored; contact support for help checking your account.

Why it works: Describe what the patch fixes and whether old data is repaired. Replace the illustrative version, behavior and recovery advice with facts from your own release.

Copy the markdown · replace illustrative details
## Version 3.4.1: a fix for offline drafts

This fictional example describes a patch for iOS and Android.

- Drafts saved offline no longer disappear from the list after reconnecting.
- The retry message now explains when a connection is needed.

Update from your device's app store when version 3.4.1 becomes available. Previously missing drafts are not automatically restored; contact support for help checking your account.

What makes a great changelog?

  • Lead with the user-visible benefit, not the internal ticket title.
  • Include availability, required action and an exact UI path when relevant.
  • Use one main idea per entry; group small fixes into readable lists.
  • Support metrics with evidence and context. Never invent impact or guarantees.
  • Put deadlines and migration requirements near the top of breaking changes.
  • Link release notes from inside your product and keep the public archive searchable.
  • Distinguish a native SDK from a web embed: the LogPulse script is for websites and compatible webviews, not a native iOS or Android SDK.

Keep reading

Common questions

Keep your writing toolkit close

API changelog template →Open-source changelog template →Developer tool changelog template →B2B SaaS release notes template →8 SaaS changelog examples worth borrowing →A release notes template you can actually reuse →

Less setup. More shipping.

Give your next release an audience.

Up to 10 releases and 100 subscribers, with the ⚡ Powered by LogPulse badge. Pro is €12/month or €99/year.

Start freeTry the live widgetSee pricing