android-state-management
Learn proven patterns for managing Android screen state with full lifecycle awareness. This skill covers predictable approaches to handling UI state across configuration changes, rotations, and process recreation—essential for building stable, maintainable apps. Explore real-world examples and fixtures you can adapt to your own projects.
android-state-management teaches you to implement loading, empty, error, and success states explicitly in your UI layer. Rather than scattered boolean flags, you model these as distinct, mutually-exclusive states within a sealed class or similar structure. This makes state transitions predictable and UI rendering straightforward—each state maps directly to what users see on screen.
AI-generated summary based on this skill's SKILL.md
Install
krutikJain/android-agent-skills/android-state-management · repository language: Python
git clone https://github.com/krutikJain/android-agent-skills
cp -r android-agent-skills/skills/android-state-management ~/.claude/skills/android-state-managementFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does android-state-management help with loading, empty, error states?
android-state-management teaches you to implement loading, empty, error, and success states explicitly in your UI layer. Rather than scattered boolean flags, you model these as distinct, mutually-exclusive states within a sealed class or similar structure. This makes state transitions predictable and UI rendering straightforward—each state maps directly to what users see on screen.
What is the viewmodel state container pattern?
android-state-management covers the ViewModel state container pattern, where a ViewModel holds a single source of truth for screen state via MutableStateFlow or similar. This container exposes immutable state to the UI and receives user actions through methods or event channels. The pattern ensures state survives configuration changes and process recreation automatically.
How do you separate persistent state from one-off events in Android?
android-state-management explains that persistent state (like loaded data) belongs in StateFlow, while one-off events (like navigation or toast messages) belong in separate channels like SharedFlow or event buses. This separation prevents events from replaying on recomposition or screen rotation, and ensures your UI responds correctly to both ongoing conditions and transient user feedback.
What lifecycle-aware state holder patterns does android-state-management teach?
android-state-management covers lifecycle-aware patterns where state holders (typically ViewModels) automatically survive configuration changes and process death. By leveraging ViewModel's scoping and StateFlow's hot flow nature, your screen state persists across rotations and system recreation without manual SavedState boilerplate—keeping your code clean and predictable.
Does android-state-management cover Compose and XML layout examples?
Yes. android-state-management provides state management best practices for both Jetpack Compose and traditional XML layouts. You'll learn how to apply the same container and reducer patterns across both frameworks, ensuring consistency whether you're building new Compose screens or maintaining legacy XML-based UIs.
What anti-patterns does android-state-management help you avoid?
android-state-management identifies common pitfalls like scattered mutable state, event replay on recomposition, and state loss across configuration changes. By teaching predictable state ownership and explicit lifecycle handling, the skill helps you sidestep these traps and build screens that recover gracefully from interruptions and system-initiated recreation.
SKILL.md
rendered from the published skill — quoted content, verbatim
Android State Management
When To Use
- Use this skill when the request is about: android ui state reducer, state management in compose or xml android, one-off events in android screen.
- Primary outcome: Model screen state, events, reducers, and side effects for Android UIs with predictable lifecycle-aware ownership.
- Handoff skills when the scope expands:
android-coroutines-flowandroid-ui-states-validation
Workflow
- Confirm the user-visible journey, target
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 6 files
skills/android-state-management/SKILL.md
skills/android-state-management/agents/openai.yaml
skills/android-state-management/references/official-links.md
skills/android-state-management/references/patterns.md
skills/android-state-management/references/scenarios.md
skills/android-state-management/scripts/run_examples.sh