# Feedback and release notes for mobile apps

> Give your app's users a feedback board and release notes they can open from the settings screen. Email them when an update they asked for ships.

URL: https://office.greatwork.company/engage/for/mobile-apps
Last updated: 2026-11-21

App store reviews are a bad place to collect feature requests: you can't reply in a thread, merge duplicates or tell people when you ship. Link a Engage portal from your app's settings screen and your users get a proper place to ask, vote and read what's new.

## What gets in the way

- Feature requests buried in one-star reviews
- Release notes limited to a few lines in the store listing
- No way to tell users their request is in the latest version

## The workflow

1. **A link in settings.** Add "Suggest a feature" and "What's new" rows to your settings screen that open the portal in a browser view.
2. **Votes by email.** Users vote with an email address and no account; that email is how you'll reach them later.
3. **Full release notes.** Write each version's notes with screenshots in the changelog, labeled New, Improved and Fixed.
4. **Tell the people who asked.** Link the shipped ideas to the update so voters get an email when the version is live.

## Example: A habit tracker on version 4.2

A two-person studio links its portal from the app's settings. Over a month, 520 users vote, and "Widgets for the home screen" reaches 180 votes. Version 4.2 ships with widgets; the changelog entry has three screenshots and links the idea, and 180 people get an email saying it's in the update they just downloaded.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
