This page records what the current Flow media shows. It keeps the marketing story grounded in captured behavior, not assumptions.
Media Evidence Inventory
Use this page to understand which claims are backed by current screenshots or videos.
| Surface | Primary Assets | Evidence Status |
|---|---|---|
| Web workflow | web-board-overview.png, web-create-task.png, web-task-detail.png, web-terminal.png, web-git-history.png, web-archive.png, web-first-task-walkthrough.webm | Captures task creation, execution monitoring, terminal output, Git review, and archive flow from the local web app. |
| Mac runtime | mac-desktop-dashboard-current.png, mac-desktop-disconnected-current.png, mac-launchpad-runtime.webm | Captures desktop launchpad runtime status, recovery state, and app shell behavior. |
| Android setup | android-home-dashboard.png, android-run-command-permission.png, android-termux-connected.png, android-termux-setup-complete.png, android-termux-setup-app-next-steps.mp4 | Captures native setup steps, permission state, and Termux readiness in the Android preview path. |
| Android runtime | android-runtime-running.png, android-webview-board.png, android-termux-runtime-workflow.mp4 | Captures runtime start on port 3484 and the Flow board opening in Android WebView. |
| Android failure context | android-setup-package-failure.png, android-termux-repair-output.png | Captures a low-storage setup failure and repair output for troubleshooting context. |
Captured
| Platform | Media | Status |
|---|---|---|
| Web | screenshots and first-task walkthrough video | Captured from the live local app |
| Mac | launchpad, runtime status, disconnected recovery screenshots, and runtime-status video | Captured from the built Electron shell and shipped desktop assets |
| Android | home, permissions, Termux, ports, setup, runtime-running, WebView board screenshots, and app-guided setup/runtime video | Captured from connected Android 16 emulator |
Android Runtime Evidence
The Android setup and runtime flow was run through the ZoneGaze Flow app next-step controls on an Android 16 emulator with a 12 GB data partition:
- compatible Termux 0.118.3 was installed
- Android Run Command permission was granted to ZoneGaze Flow
- Termux external commands were enabled
- Check connection reported Termux connected
- Setup / Update launched from the app
- Setup / Update completed successfully in Termux
- Start launched the bundled ZoneGaze Flow runtime on port 3484
- Open loaded the ZoneGaze Flow board in the Android WebView
- native Home, Permissions, Termux, Ports, runtime-running, and WebView screens were captured from the emulator app
The completed runtime video is:
/docs/flow/assets/videos/android-termux-runtime-workflow.mp4Earlier Android Capture Failure
An earlier Android emulator had only about 281 MB free on /data during setup. Termux package upgrade failed with apt/dpkg missing-archive errors such as:
dpkg: error: cannot access archive '/data/data/com.termux/cache/apt/archives/dash_0.5.12-2_aarch64.deb': No such file or directoryThat failure is kept as troubleshooting context only. It is not current Android runtime evidence.
Claim Boundaries
The media supports product-behavior claims only within the captured environments:
- Web captures support the Flow board, task, terminal, Git, and archive workflow shown in the assets.
- Mac captures support the desktop launchpad and runtime recovery behavior shown in the assets.
- Android captures support a connected Android 16 emulator path with compatible Termux, Run Command permission, setup/update completion, runtime start, and WebView board load.
- Earlier Android setup failure media supports troubleshooting guidance, not current runtime success.
- Download, packaging, public access, support, and device-coverage claims still need separate release and support evidence.
Use This Evidence
Use current media when writing product pages, platform docs, support answers, demos, and launch updates:
- Link to Media gallery when a reader needs to inspect the screenshots or videos.
- Link to Platform notes when the question is which surface to use.
- Link to Troubleshooting when the question is blocked setup, runtime, Termux, terminal, or Git state.
- Keep Android preview language tied to the captured emulator, Termux, permission, setup, runtime, and WebView evidence.
Media Routes
- Media gallery lists every screenshot and video.
- Platform notes explains web, Mac, Android, and CLI readiness.
- Troubleshooting separates current runtime evidence from failure context.
Leave with a concrete next action.
Each doc page should end with a command, route, verification step, screenshot, or support packet users can act on.
Do not strand the reader.
Link to the next workflow page, install guide, troubleshooting, demos, downloads, or support depending on the page topic.