Begin of the insertion### User Story

**As an** app userEnd of the insertion Begin of the deletion **As** a \[enter role of user\]End of the deletion
**I Begin of the insertionwant** to be informed when the app is caching data in the backgroundEnd of the insertion Begin of the deletion want to** \[enter objective\]End of the deletion
**so Begin of the insertionthat I** understand why the app may be doing work and how it improves performance.End of the insertion Begin of the deletion that** \[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 insertionWhen the app starts a background caching process that is intended to speed up future app usage, a toast banner is displayed to the user.

End of the insertion Begin of the deletion <br>


**Technical notes**

End of the deletion * Begin of the insertionThe toast banner is displayed only while background caching is actively in progress.

End of the insertion Begin of the deletion <br>


**Permissions and visibility considerations**

End of the deletion * Begin of the insertionThe toast banner automatically disappears immediately after the caching process completes successfully. Followed by another success banner that also gets automatically dismissed after some seconds or the user press on the X action.

* The toast bannerEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionnot shown if no caching is needed.

* The toast banner is presented as a non-blocking UI element that does not prevent navigation or interaction with the app.

* The toast banner content matches the mockups:

* Title: **“Optimizing your experience”**

* Body: **“We’re saving data to help the app load faster next time. Please don’t close the app whileEnd of the insertion this Begin of the insertionfinishes.”**

* The toast banner includes a leading download/processing icon as shown in the mockups.End of the insertion Begin of the deletion feature visible?_End of the deletion

* Begin of the insertionThe toast banner appears anchored at the bottom of the screen above the bottom navigation bar (does not overlap the nav items).

* The toast banner respects device safe areas and does not get clipped by screen corners or home indicator areas.

* The toast bannerEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionreadable in both light and dark mode (or uses the app’s standard toast styling that meets contrast requirements).

* The toast banner does not stack multiple times if multiple caching subtasks start while one caching session is already in progress.

* If caching is restarted while the toast is visible (e.g., additional data caching is triggered), the toast remains visible without flickering or resetting animations.

* If caching fails:

* The toast banner is dismissed.

* No error toast is shown unless explicitly specified elsewhere (failure handling is limited to removal of this informational banner).

* If the user backgrounds the app while caching is in progress and returns before completion:

* The toast banner is visible again on return until caching completes.

* If the user backgrounds the app and the OS terminatesEnd of the insertion it Begin of the insertionduring caching:

* On next launch, the toast banner is shown again only if caching resumes or is required.

* The toast banner isEnd of the insertion not Begin of the insertiondisplayed on screens where toast banners are explicitly disallowed by platform guidelines (if such screens exist), otherwise it can appear on any screen.

* The toast banner behavior is consistent across iOS and Android.End of the insertion Begin of the deletion visible?_End of the deletion


Begin of the insertion### Technical NotesEnd of the insertion Begin of the deletion **Translation considerations**End of the deletion

* Begin of the insertionAssumptions:

* “Caching” refers to downloadingEnd of the insertion Begin of the deletion _Key termsEnd of the deletion and Begin of the insertionpersisting data locally (e.g., API responses, metadata, configuration) to improve subsequent load times.

* There is a single logical “caching session” that may consist of multiple subtasks.

* State model:

* Maintain a global observable state, e.g. `cacheWarmupState = idle | in_progress | completed | failed`.

* The toast is visible iff `cacheWarmupState == in_progress`.

* Triggering conditions:

* The toast is shown when the caching session starts (transition to `in_progress`).

* The toast is hidden when the session transitions to `completed` or `failed`.

* Concurrency and de-duplication:

* Ensure multiple triggers for caching do not create multiple toasts.

* If multiple subtasks exist, aggregate them under one session and only transition to `completed` when all required subtasks finish.

* Persistence and lifecycle:

* The toast visibility should be derived from runtime state, not persisted storage.

* If the app resumes and caching is still running, the state should rehydrate to `in_progress` so the toast shows again.

* Performance:

* Toast rendering must not block caching work.

* Avoid frequent UI updates; update only on state transitions, not on per-item caching progress unless a progress UI is explicitly requested.

* Telemetry (optional, if existing analytics permits):

* Track `cache_warmup_started`, `cache_warmup_completed`, `cache_warmup_failed` with duration to assess performance wins and failure rates.


### Permissions and Visibility Considerations

* The toast is visible to any user using the app when background caching isEnd of the insertion Begin of the deletion phrasesEnd of the deletion in Begin of the insertionprogress.

* No role-based restrictions apply unlessEnd of the insertion the Begin of the insertioncaching feature itself is restricted (not implied by the input).End of the insertion Begin of the deletion key languages_&nbsp;End of the deletion


Begin of the insertion### 5\. Translation ConsiderationsEnd of the insertion Begin of the deletion **Out of scope**End of the deletion

* Begin of the insertionStrings requiring localization:

* “Optimizing your experience”

* “We’re saving dataEnd of the insertion Begin of the deletion <br>


_Set the_ **To be informed/consulted teams** _fieldEnd of the deletion to Begin of the insertionhelp the app load faster next time. Please don’t close the app while this finishes.”

* &quot;App optimized&quot;

* Must NOTEnd of the insertion Begin of the deletion include all teams necessary toEnd of the deletion be Begin of the insertiontranslated:

* Any internal state keys or event names (e.g., `cacheWarmupState`, `cache_warmup_started`)

* Icon identifiers (asset names)


### 6\. OutEnd of the insertion Begin of the deletion informedEnd of the deletion of Begin of the insertionScope

* Showing a progress bar, percentage, or detailed list of what is being cached.

* AllowingEnd of the insertion the Begin of the insertionuser to dismiss the toast manually (not requested; toast is state-driven).

* Adding retry UI or explicit error messaging for caching failures.

* Adding a settings toggle to disable caching or disable the toast.End of the insertion Begin of the deletion changes._End of the deletion