Content
View differences
Updated by Marc Alcobé about 16 hours ago
**As a** mobile app user
**I want to** see “What’s new” in the app
**so that** I can quickly understand newly delivered
### Acceptance Criteria
* The app shows a “What’s new” entry point (“What’s new”) that opens a list of available updates (card list).
* On 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** button and does not block subsequent usage after dismissal.
* The “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” experience is accessible 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).
* If the app is opened multiple times after the same major release, the “What’s new” auto-popup is not shown again.
* If no “What’s new” content is configured for the current app version/release, no auto-popup is shown and Settings access displays either an empty state or the latest available items (behavior defined in Technical Notes).
* The “What’s new” screen respects app theming (light/dark mode) as shown in the Settings context.
* Once a new major release happens with new "What's new" the previous assets for the old release should be removed.
* Ensure this works also with the PMFlexONE application. application
* For this first release we will include what's new screens for three things developed between 0.3.0 and 0.4.0:
* Meetings
* Time tracking views
* Switch instances
### Technical Notes
<br>
### Permissions and Visibility Considerations
* Visibility:
* The “What’s new” popup is shown to users who can access the mobile app.
* If the app supports multiple instances/environments, “What’s new” content and “seen state” must be separated per instance.
* Role-based content targeting:
* Support targeting by role (e.g., admin/member) only if the backend 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.
* Remove the localization of the previous whats new releases to reduce amount of translatable strings.
### 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.
**I want to** see “What’s new” in the app
**so that** I can quickly understand newly delivered
### Acceptance Criteria
* The app shows a “What’s new” entry point (“What’s new”) that opens a list of available updates (card list).
* On 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** button and does not block subsequent usage after dismissal.
* The “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” experience is accessible 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).
* If the app is opened multiple times after the same major release, the “What’s new” auto-popup is not shown again.
* If no “What’s new” content is configured for the current app version/release, no auto-popup is shown and Settings access displays either an empty state or the latest available items (behavior defined in Technical Notes).
* The “What’s new” screen respects app theming (light/dark mode) as shown in the Settings context.
* Once a new major release happens with new "What's new" the previous assets for the old release should be removed.
* Ensure this works also with the PMFlexONE application.
* For this first release we will include what's new screens for three things developed between 0.3.0 and 0.4.0:
* Meetings
* Time tracking views
* Switch instances
### Technical Notes
<br>
### Permissions and Visibility Considerations
* Visibility:
* The “What’s new” popup is shown to users who can access the mobile app.
* If the app supports multiple instances/environments, “What’s new” content and “seen state” must be separated per instance.
* Role-based content targeting:
* Support targeting by role (e.g., admin/member) only if the backend 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.
* Remove the localization of the previous whats new releases to reduce amount of translatable strings.
* 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.