Android Kit is opinionated. It owns the shape, typography, geometry, predefined icons and labels, control arrangement, accessibility semantics and interaction behavior of its components.
What the application supplies
- Typed content and domain data.
- State, callbacks and availability options.
- Supported placement and layout choices.
- The theme palette and supported component colors.
- Application body content in page, card, sheet and navigation body slots.
Public component APIs do not expose arbitrary rendering slots for headers, controls, menus, settings rows or badges. See themes for the color-only appearance contract.
Application-owned content
Your application owns its content styling, routes, authentication, permissions, business rules and domain persistence. Kit’s body slots let you compose that content within the shared presentation.
Apply the managed content padding supplied by pages and sheets to the scrolling content. This lets the viewport remain edge-to-edge while clearing the component’s measured chrome and system insets.
Cards also accept optional visual-only trailing content for application-owned indicators. Kit reserves space and supplies the supported trailing-content color; the application supplies the localized description, state and actions. Keep this slot non-interactive. Pin persistence and ordering belong to the application.
Typed controls and actions
Use section cards for typed rows and controls. Declare menu entries through the action flyout DSL; Kit renders their icons, text, spacing and dismissal behavior.
Lists accept application-owned visual-only item
bodies while Kit owns the lazy container, item spacing, adaptive grid columns,
item interaction, menus, selection and supported swipe actions. Use the complete
AndroidKitList in either List or Grid mode; its low-level item helpers are
internal. Share the list state’s selection with page and navigation chrome.
Settings and history
Declare one complete Settings catalog in an owner above Settings navigation. Main, About and subpages share its catalog, persistent values, search history and privacy state.
Independent content searches keep a separate history and privacy scope for each logical page.
Shared vocabulary
Kit owns predefined control wording and translations. Your application owns content labels, custom action labels, option values and domain messages. Consumers must apply the localization build gate.