Release 0.1.3 with the aperture startup animation
All checks were successful
Validate and publish Kaleido / android (push) Successful in 2m15s

The cold-start splash is now an iris: the closed aperture gathers light,
twists open with light leaking through its gaps, a sheen crosses the mark
and the wordmark slides out from behind it. The exit flies through the
aperture's center into the app instead of crossfading. The iris holds while
startup data arrives so cold-start hitches never land mid-motion.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Elijah 2026-10-24 10:58:15 -07:00
parent 430616330b
commit 4c56eb3755
9 changed files with 256 additions and 73 deletions

View file

@ -70,3 +70,11 @@ For a quiet device with system effects already enabled, run `python -c "import s
Private evidence includes `home-baseline-results.json`, `home-trace-baseline-atrace.txt`, `home-complete-results.json`, `home-complete-cold-results.json`, `navigation-audio-results.json`, `navigation-audio-off-atrace.txt`, `navigation-audio-on-atrace.txt`, and the On/Off setting screenshots. `Build.ps1 -Release -Test` passed with three unit tests and zero lint errors. These measurements were taken on the local optimized test build before versioning the changes as 0.1.2. The installed test build retains the existing session and was left on Home with navigation sounds On.
All six `verify_ui.py browse` checks passed with the sound setting and cache window, including focus restoration, separate Movies/TV layouts, A–Z grids and PIN cancellation preserving the session. The broader `repro_runtime.py browse` check initially failed at p95 42 ms (48 ms with tracing), with further card composition/measurement during rapid movement. Including the new sound modifier/controller in the app's baseline profile brought the final profiled release to median 15 ms / p95 36 ms, GPU p95 7 ms, and stable horizontal Y coordinates at 182 px. Some stress-test frames still miss 60 Hz. `browse --trace` now records this exact regression loop to `browse-regression-atrace.txt` for future diagnosis.
## Aperture startup animation - 2026-10-24
The cold-start splash was prototyped as a dp-accurate canvas page (ignored `evidence/private/splash/index.html`), approved, then ported to `StartupSplash.kt` with the same geometry, timings and cubic-bezier curves. The exit cuts the aperture's inner hexagon out of the splash surface with an even-odd path and zooms it about 52× in log space, so the real app beneath is revealed through the mark; the content layer scales from 1.14 to 1 only while the cover exists.
Frame statistics from three profiled release cold starts (`dumpsys gfxinfo framestats`, bucketed per 250 ms) first showed 100–125 ms frames about 0.3–0.7 s after launch: startup data arriving and Home composing beneath the splash, with high UI-thread time. Starting the animation a few frames late did not avoid them because they follow the data, not the first frame. Skipping the hidden app's draw until the exit made no measurable difference and was reverted. The final sequence instead runs a 260 ms light-gathering phase on the nearly still closed iris, then holds until `busy` clears and four consecutive frames arrive within 24 ms (capped at 700 ms). On the final build every frame from the iris opening through the start of the exit completed within 25 ms in all three runs, at 15 frames per 250 ms. Frames after the reveal include Home itself and show higher latency without dropping below 15 frames per bucket. These are device samples, not a guarantee.
The hold adds roughly 0.5 s before the iris opens when Plex data takes that long; loading previously overlapped the animation. `Build.ps1 -Release -Test` passed; `repro_runtime.py sections` passed and all six `verify_ui.py browse` checks passed on the final release. A screen recording of the actual cold start (`kaleido-aperture-startup.mp4`, contact sheet `aperture-sheet.png`) was inspected. The optimized release was left on Home.