Android Room Database

When To Use

• Use this skill when the request is about: room database android, dao query migration android, room schema export.
• Primary outcome: Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.
• Reach for this skill when the hard part is schema design, DAO queries, transactions, migrations, or Room testing. Hand off to android-rxjava-to-coroutines-migration only if the main work is reactive API migration rather than the database contract itself.
• Handoff skills when the scope expands:
• android-local-persistence-datastore
• android-testing-unit

Workflow

1. Start with the persistence contract: entities, keys, indexes, relations, and whether the data is source-of-truth, cache, or offline-first state.
2. Model DAO access patterns explicitly, including transaction boundaries, query shape, paging, and invalidation behavior.
3. Plan schema evolution before changing entities: exported schemas, migration steps, auto-migration eligibility, and destructive-fallback policy.
4. Validate migration and query behavior with deterministic tests rather than assuming Room annotations are enough.
5. Hand off DataStore, sync, or reactive API questions only after the Room boundary is correct.