See shotfleet work
Short clips of the commands, then a dated record of what shotfleet has been run on and what happened.
Clips
The clips are real terminal recordings from one session on the fixture apps in shotfleet's own repository; titles, subtitles and the sped-up labels were added afterwards.
Is this Mac ready?
Set up a project
Evidence
What has been run, when, and what came out. Only what is recorded is listed; the note under each line names the record in shotfleet's repository.
Built for macOS 13 or later on Apple silicon; tested on macOS 27.
Releases
- 2026-10-05, release 0.1.2. The signed build ran the fixture app on iPhone and iPad simulators and an Android emulator and passed 65 of 65 assertions in 37 minutes. Record: research/0.1.2-plan.md (Outcome), docs/handoff.md section 15, docs/compat.md
- 2026-10-05, same run. In the iPad part the Mac was heavily loaded and 3 of 4 simulators stopped answering; shotfleet finished all 4 languages on the 1 simulator left, with 0 problems. Record: docs/handoff.md section 15, research/0.1.2-plan.md
- 2026-10-05, release 0.1.1. On GitHub's hosted Apple silicon runners with macOS 14.8.9 and 15.7.9, the installer, shotfleet --version, doctor and check all ran; no simulator or emulator was run there. Record: research/limits-platform-reach-2026-10-05.md, docs/compat.md
Real apps
- 2026-10-01 and 2026-10-04, my app, WOD Tracker. 18 languages on iOS and Android, 0 problems, on Maestro 2.0.10. Then 19 languages each on iOS, an Android phone and an Android tablet, 0 problems, on Maestro 2.11.0; 9 iOS languages needed shotfleet's retry. Record: PLAN.md, docs/compat.md, research/maestro-2-11.md
- 2026-10-05, timing. WOD Tracker in 19 languages on 4 simulators and 4 emulators with Maestro 2.0.10: 404 s of capture on iOS and 415 s on Android phones, 0 problems, no retries. The Mac was not idle: its load went from 86 to 497 during the iOS part. Record: docs/compat.md, research/workarounds-maestro-resources-2026-10-05.md
- 2026-10-03, wger (Flutter). iOS and Android, German and Japanese: German on every screenshot. wger's Japanese is about 30% translated, so those screens show English, and check said so. Record: research/frameworks.md section 15, research/real-apps-2026-10-03/
- 2026-10-03, the obytes template (Expo). iOS and Android, English and Arabic, with Arabic right to left on the Settings screen. Its onboarding and login screens are hard-coded English, and check flagged them. Record: research/frameworks.md section 15, research/real-apps-2026-10-03/
- 2026-10-03 and 2026-10-04, the KotlinConf app (Compose Multiplatform). Android, German and English: 6 screenshots, 0 problems. On iOS its first screen came out blank (it draws after its text is readable) and check flagged it; a clean iOS run is still to do. Record: research/frameworks.md sections 15 to 17, research/real-apps-2026-10-04/
- 2026-10-04 and 2026-10-05, Microsoft's .NET MAUI localization sample. Five languages on iOS and two on Android, one screen each: 0 untranslated selectors and 0 problems. Not yet a real MAUI app or a Release build. Record: research/frameworks.md section 5, research/experiments-2026-10-04/C/ and C2/
- 2026-10-04 and 2026-10-05, a small Capacitor test app. The per-app language reached its web view on iOS 26.4, iOS 18.6 and Android 16. Maestro read the web view's text on iOS but not on Android. This tested the language only, not a full shotfleet run. Record: research/frameworks.md section 7, research/experiments-2026-10-04/B/ and B2/
New in 0.1.3
- 2026-10-05, release 0.1.3. On Android, shotfleet reads the screen text from Maestro's UI hierarchy instead of from pixels. On the Android fixture app it passed 30 of 30 assertions with Maestro 2.11.0, and 29 of 29 with Maestro 2.0.10, where it still reads pixels. Record: pull request 44, branch claude/013-android-hierarchy (claims row C132)