datastore

Manage Android key-value data with DataStore and Kotlin coroutines.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/eygraber/jellyfin-kmp --skill datastore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datastore
Source: https://github.com/eygraber/jellyfin-kmp/tree/main/.claude/skills/datastore
Command: npx skills add https://github.com/eygraber/jellyfin-kmp --skill datastore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DataStore provides a simple, reactive key-value persistence layer for Android apps, offering a modern alternative to SharedPreferences for lightweight configuration data.

Core Features & Use Cases

  • Create and manage simple preferences with typed keys.
  • Read values with defaults and observe changes via Flow.
  • Migrate from SharedPreferences and handle small configuration data across app components.

Quick Start

Initialize a DataStore instance and perform read/write operations using Kotlin coroutines and Flow as demonstrated.

Frequently Asked Questions about datastore

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

FAQPage Schema
How do I persist key-value data in Android using Kotlin DataStore?

Persist key-value data in Android by initializing a DataStore instance and performing read/write operations using Kotlin coroutines and Flow to manage user preferences and simple settings.

What is the best way to migrate SharedPreferences to DataStore for app preferences?

Migrating SharedPreferences to DataStore involves using built-in data migration guidance to safely transfer lightweight configuration data into a modern, reactive key-value persistence layer.

Does DataStore support observing preference changes reactively?

Yes, DataStore supports observing preference changes reactively via Kotlin Flow, allowing app components to read values with defaults and dynamically react to configuration updates.

When should I use DataStore for lightweight configuration data in Android apps?

Use DataStore for lightweight configuration data in Android apps when you need typed keys, default values, and simple settings management across app components without the overhead of a full database.

Can I use DataStore to manage typed keys and default values for user settings?

Yes, you can use DataStore to manage user preferences by creating typed keys and defining default values, ensuring type-safe reads and writes across your Android application components.

Why choose DataStore over SharedPreferences for Android persistence?

Choose DataStore over SharedPreferences to replace synchronous calls with asynchronous data access, leveraging Kotlin coroutines and Flow for safer, non-blocking key-value persistence and data migration.