> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/release-notes/mobile/2026/mobile-app-release-1-5-0.md). # Mobile App Release 1.5.0: Event Flow and Alarm Camera Snooze October 28, 2026 The Solink Mobile App was updated on both iOS and Android with the following changes. ## Enhancements This release adds the following enhancements: * [**Event Flow**](/docs/review-events-and-save-evidence/events/event-flow.md): Authorized users can now complete guided event reviews directly in the app and view results instantly. * [**Talk Down via Speaker**](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/calling-sip-enabled-speaker-via-solink-platform.md): Look for the new speaker icon on camera feeds to quickly see which cameras support talk down: A camera feed in the mobile app with the speaker icon * [**Alarm Camera Snooze**](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/snooze-alarms.md): Alarm users with permissions can now snooze alarm cameras for an entire site or for individual cameras. ## Bug Fixes This release fixes the following issues: * Resolved an issue where AI Dashboard conversion rate widgets did not show data. * Fixed an issue that caused video playback to get stuck loading on some devices. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/release-notes/mobile/2026/mobile-app-release-1-5-0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.