Android ViewSystem Foundations

When To Use

• Use this skill when the request is about: xml layout android issue, fragment lifecycle android, constraintlayout cleanup.
• Primary outcome: Handle XML layouts, ConstraintLayout, Fragments, ViewBinding, DataBinding, and classic Android UI lifecycle patterns.
• Reach for this skill when the main surface is XML, Fragment, RecyclerView, or binding lifecycle work rather than Compose-first UI.
• Handoff skills when the scope expands:
• android-compose-xml-interoperability
• android-testing-ui

Workflow

1. Identify whether the target surface is Fragment, Activity, custom view, RecyclerView, or a mixed Compose/View interoperability screen.
2. Anchor ownership correctly: view bindings to the view lifecycle, adapters to explicit item models, and navigation/transactions outside leaf views.
3. Fix layout and rendering issues with classic View tools first: ConstraintLayout, RecyclerView diffing, window insets, and binding-safe updates.
4. Exercise Fragment recreation, long text, font scaling, RTL, and process-lifecycle edges before considering the change complete.
5. Hand off Compose interoperability or UI test depth only after the View-system ownership model is stable.

Guardrails

• Optimize for stable state and predictable rendering before adding animation or abstraction.
• Respect accessibility semantics, contrast, focus order, and touch target guidance by default.