Backdrop

Backdrop

Use this skill for Kototoro's io.github.kyant0:backdrop integration. The app uses Backdrop for the iOS interface style and Haze for the other runtime glass path; do not substitute Haze APIs when the affected code imports com.kyant.backdrop.

Workflow

1. Locate the drawBackdrop call and identify its source (LocalLiquidGlassBackdrop, rememberLayerBackdrop, or layerBackdrop). Confirm the source and destination are in the same window; Popup/Dialog content normally needs the regular GlassSurface fallback.
2. Read the complete modifier chain. Backdrop effects transform the sampled backdrop, but they do not provide an opaque semantic container color. Add a theme-derived surface tint with onDrawSurface when content needs stable contrast.
3. Keep effect order as color filter -> blur -> lens. lens requires a CornerBasedShape; use a simpler shape or omit lens for arbitrary shapes.
4. Keep colors theme-aware. Never use an opaque/fixed white surface as the iOS default. Derive the base from MaterialTheme.colorScheme.surfaceContainer (or a more suitable surface role), then apply a modest alpha after drawBackdrop.
5. Preserve content color separately from the surface tint. Use MaterialTheme.colorScheme.onSurface for standard iOS glass controls unless the component has a stronger semantic role.
6. Remember that drawBackdrop enables Highlight.Default and Shadow.Default unless explicitly overridden. Prefer those Backdrop-native layers over wrapping the same glass shape in a Compose elevation shadow.
7. Do not place a same-shape clip outside drawBackdrop; the modifier already clips the glass content to shape, while an outer clip can cut off Backdrop's expanding shadow and highlight.
8. Do not animate alpha on a parent that contains an out-of-bounds Backdrop shadow. Compose uses an offscreen layer while alpha is below 1f, clipping the expanded shadow to the parent's bounds. Prefer translation-only entrance and exit animations for glass chrome.
9. Validate with ./gradlew :app:compileDebugKotlin --no-daemon. Add or update a focused unit test when extracting pure color or modifier-policy logic.

Kototoro conventions

• iOS detection is LocalInterfaceStyle.current == InterfaceStyle.IOS.
• The active Backdrop is provided by LocalLiquidGlassBackdrop.current.
• Existing shared glass code belongs in core/ui/glass or core/ui/compose; prefer a small Modifier helper over duplicating a long background + drawBackdrop + border chain.
• drawBackdrop can use exportedBackdrop = rememberLayerBackdrop() when a child surface should feed another Backdrop surface.
• Surface tint must be drawn after the visual effect. Prefer onDrawSurface so the surface participates in the same shaped glass layer; otherwise place a .background(...) modifier after .drawBackdrop(...).
• A uniform white or black backdrop remains nearly uniform after blur and lens. Regular navigation glass must establish a subtle internal luminance difference with a semantic surface tint; shadow is only a secondary depth cue.
• Treat GlassStyle.containerAlpha as a material-density input. It must influence the final surface tint, but it does not need to be copied one-to-one because Backdrop surface compositing becomes nearly opaque at the values used by stable Material surfaces.
• If drawBackdrop uses its default or an explicit Backdrop shadow, do not also call glassContainerShadow or Modifier.shadow for the same shape.
• Place top-bar controls inside the shared mainTopBarHeight slot and size them with topBarButtonSize; the difference is required shadow breathing room. If a tag rail follows the bar, clip only the collapsing slot while it is actually collapsed, not the fully expanded chrome column.
• Popup windows have a different coordinate space. Do not assume the root Backdrop is valid inside a Popup; use the existing root overlay route or fallback surface pattern.

Diagnosis checklist

• Is the control's surface tint fixed to Color.White or Color.Black?
• Is the tint before drawBackdrop, and therefore potentially hidden by the effect?
• Is the control inheriting a transparent container from Material components?
• Is onDrawSurface already drawing a tint, causing an overly opaque double layer?
• Is a .background(...) duplicating a tint already drawn by onDrawSurface?
• Is an outer clip cutting off Backdrop's native shadow or highlight?
• Is a parent fade temporarily clipping the expanding shadow in an alpha offscreen layer?
• Are Backdrop Shadow and Compose Modifier.shadow both active for the same glass container?
• On a pure-white test background, does the surface itself differ in luminance, or is only the shadow visible?
• Does the selected icon/text color match the polarity of the theme surface?
• Does a lens effect receive a CornerBasedShape and valid dimensions?

References

Read references/backdrop-api.md for the upstream API facts used by this skill, especially when changing effect order, backdrop sources, or surface drawing.