Prototype glass surfaces and custom AGSL shaders¶
- Kind: decision
- Date: 2026-10-27
- Source: moved from
how-it-works/plat/android/prototype-ux.md; #15244, #15256, #15562, #15617 - Shaped: Agent-authored prototype specification
Context¶
Two owner decisions bounded prototype surface effects: what style.surface: "glass" may draw, and
whether a spec may carry shader code at all. The spec otherwise accepts no code.
Options¶
Not recorded.
Decision¶
- Glass (2026-10-27).
style.surface: "glass"requires real glass andprototype_glass_v1: iOS 26+ Liquid Glass, and Android API 31+ real backdrop blur once its renderer exists. Android below API 31 and iOS 17–25 refuse glass by not advertising the capability. There is no simulated translucent fill,ultraThinMaterialsubstitute or fallback capability. Android rendering and device verification remain with the Android renderer slice. - Custom shaders (2026-10-26). Android-only custom AGSL shaders require
prototype_custom_shaders_v1and the host opt-inAUTOMOBILE_PROTOTYPE_CUSTOM_SHADERS=1(off by default). Source assets useapplication/vnd.automobile.agsl, valid UTF-8, at most 16 KiB, with at most 16 scalaruniform float name;declarations and one optionaluniform shader content;, so only the node’s own rendered content may be sampled. The lexical rules, reserved names and uniform value range are the contract in the shaped page. The Android runtime compiles onput_prototype_assetbefore retaining source and caps returned errors at 2 KiB of UTF-8. Execution fails closed under the frame-budget guard. iOS agents and ProtoViewer bundle import/export refuse both the MIME type andstyle.shader.
Consequences¶
Glass and shaders stay capability-gated with no degraded rendering path. The shared validators enforce the shader lexical rules on the host and the device.