adaptive

Adapt Jetpack Compose layouts for multiple Android device form factors.

Updated Apr 5, 2026

Search Tags:#android #compose #navigation3 #material3 #responsive layouts #foldables #adaptive ui

Ready to run

npx skills add https://github.com/inehemiasm/AiAssistant --skill adaptive-inehemiasm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adaptive
Source: https://github.com/inehemiasm/AiAssistant/tree/main/skills/adaptive
Command: npx skills add https://github.com/inehemiasm/AiAssistant --skill adaptive-inehemiasm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Android developers transform fixed layouts into responsive interfaces that work consistently across phones, tablets, foldables, desktops, TV, Auto, and XR devices.

Core Features & Use Cases

Adaptive Compose Layouts: Guide UI migrations using Navigation 3 Scenes, adaptive navigation components, Grid, FlexBox, and MediaQuery APIs.
Multi-Form-Factor Support: Handle changing window sizes, device postures, pointer devices, keyboards, and viewing distances with responsive layouts.
Use Case: Improve a Jetpack Compose productivity app so a phone uses bottom navigation while tablets use navigation rails and larger screens display list-detail panes.

Quick Start

Use the adaptive skill to review my Jetpack Compose app UI and update it for phones, tablets, and foldable devices.

Frequently Asked Questions about adaptive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build adaptive Jetpack Compose layouts for foldables and tablets?▼

Adaptive Jetpack Compose layouts use MediaQuery, Grid, and FlexBox APIs to adjust UI components dynamically for foldables and tablets. You migrate fixed layouts into responsive interfaces that react to changing window sizes and device postures for consistent multi-form-factor support.

What is the best way to handle navigation in responsive Android apps across different screen sizes?▼

Handling navigation in responsive Android apps involves switching between bottom navigation for phones and navigation rails for larger screens. Navigation 3 Scenes guide these adaptive navigation component migrations to ensure consistent layout patterns across varying window sizes.

Does this adaptive UI approach support non-phone Android devices like TV, Auto, and XR?▼

Adaptive UI support extends to TV, Auto, and XR devices. The approach handles changing viewing distances, pointer devices, and keyboards using responsive Compose layouts, ensuring interfaces adapt consistently across all Android app form factors.

How do I update an existing Compose app to use list-detail panes on larger screens?▼

Updating a Compose app for larger screens involves applying adaptive layout patterns like list-detail panes. The skill reviews existing UI and guides migrations using Navigation 3 Scenes and MediaQuery to satisfy multi-device layout requirements.

Can I use Navigation 3 Scenes to manage device posture changes in foldable Compose apps?▼

Navigation 3 Scenes manage device posture changes in foldable Compose apps by restructuring layouts dynamically. They work with adaptive navigation components to transition UI elements seamlessly when window sizes or physical folding states change.

What testing workflows are needed for multi-device Android responsive layouts?▼

Testing workflows for responsive layouts validate UI behavior across varying window sizes, postures, and pointer devices. They require verifying adaptive Compose APIs, Grid, and FlexBox components to ensure consistent interface rendering across phones, foldables, and tablets.