Begin of the insertion**As a** mobile app userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I want to** Begin of the insertionsee “What’s new” in the appEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can quickly understand newly deliveredEnd of the insertion Begin of the deletion \[enter desired result\]End of the deletion

Begin of the insertion### Acceptance CriteriaEnd of the insertion Begin of the deletion **Acceptance criteria**End of the deletion

* Begin of the insertionThe app shows a “What’s new” entry point (“What’s new”) that opens a list of available updates (card list).

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionOn first app open after a **major release**, the “What’s new” experience is shown automatically as a modal/popup.

* The modal/popup can be dismissed via an **X** buttonEnd of the insertion Begin of the deletion <br>


**PermissionsEnd of the deletion and Begin of the insertiondoes not block subsequent usage after dismissal.

End of the insertion Begin of the deletion visibility considerations**

End of the deletion * Begin of the insertionThe “What’s new” modal/popup supports a multi-step flow for multiple announcements (e.g., “Next” between items, and “Done” on the last item).

* The “What’s new” modal/popup supports “Skip all” to exit the flow immediately.

* The flow shows a visible progress indicator reflecting the current step out of total steps.

* Each “What’s new” item includes:

* A title

* A short description (1–3 lines)

* A visual (illustration/screenshot) consistent with the mockups

* The “What’s new” experienceEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionaccessible again from **Settings** → “What’s new”, and opens the same content.

* When accessed from Settings, the “What’s new” experience does **not** change whether the user will see the auto-popup again.

* The auto-popup is shown only once per major release per user/device (unless the user reinstalls, logs out, or local storage is cleared—behavior defined in Technical Notes).End of the insertion Begin of the deletion this feature visible?_End of the deletion

* Begin of the insertionIf the appEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionopened multiple times after the same major release, the “What’s new” auto-popup isEnd of the insertion Begin of the deletion itEnd of the deletion not Begin of the insertionshown again.

End of the insertion Begin of the deletion visible?_


**Translation considerations**

End of the deletion * Begin of the insertionIf no “What’s new” content is configured for the current app version/release, no auto-popup is shownEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionSettings access displays either an empty state or the latest available items (behavior definedEnd of the insertion Begin of the deletion phrasesEnd of the deletion in Begin of the insertionTechnical Notes).

* The “What’s new” screen respects app theming (light/dark mode) as shown inEnd of the insertion the Begin of the insertionSettings context.

End of the insertion Begin of the deletion key languages_&nbsp;


**Out of scope**

End of the deletion * Begin of the insertionFor this first release we will include what&#x27;s new screens for three things developed between 0.3.0 and 0.4.0:

* Meetings

* Time tracking views

* Switch instances


### Technical Notes

End of the insertion <br> Begin of the insertion

### Permissions and Visibility Considerations

* Visibility:

* The “What’s new” popup is shownEnd of the insertion Begin of the deletion


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the insertionusers who can access the mobile app.

* If the app supports multiple instances/environments, “What’s new” content and “seen state” mustEnd of the insertion Begin of the deletion include all teams necessary toEnd of the deletion be Begin of the insertionseparated per instance.

* Role-based content targeting:

* Support targeting by role (e.g., admin/member) only ifEnd of the insertion Begin of the deletion informed ofEnd of the deletion the Begin of the insertionbackend can reliably determine the user’s role at fetch time.

* If targeting is enabled, ensure users only receive content intended for their role.


### Translation Considerations

* Localize:

* “What’s new”, “Next”, “Done”, “Skip all”, and any empty/error state text.

* Titles and descriptions for each “What’s new” item.


### Out of Scope

* Building a full “Release notes” system with changelog filtering by project/type.

* Notifications (push/email) about new releases; this is strictly an in-app surface.End of the insertion Begin of the deletion changes._End of the deletion