Introduction

Store reads and writes data that lives in more than one place: a network, a local database, and memory. Store 6 is the next major line. Store 5 continues under its own coordinates for the whole 6.x major.

Why Store?

Reading data across those boundaries means coordinating freshness, failures, deduplicated fetches, and cache bounds by hand around every endpoint. Store gives your application one typed contract for those reads and writes on every Kotlin platform, so that coordination is written once and tested once.

Store 6: start here

• Store 6 introduction: What Store 6 is and where to start.
• Store 6 quickstart: Build the five-line store and run the full program.
• Important defaults: See every zero-config behavior, each traced to a named conformance test.
• Migrate from Store 5: Move one screen at a time while both coordinate lines live side by side.

Store 5: maintained legacy

Store 5 documentation remains available. store5.* and store6.* coordinates live side by side for the whole 6.x major, and store6-store5-interop is supported for all of 6.x.

• Meet Store: Meet Store and find its core resources.
• Why Store?: Understand the Store 5 model and capabilities.
• Store 5 quickstart: Build your first Store 5 store.
• Store 5 concepts: Browse the Store 5 components and their roles.

Which track am I on?

• New project: Start with the Store 6 introduction.
• Existing Store 5 app: Keep the Store 5 documentation and read Migrating from Store 5 when you are ready. The Store 5 to Store 6 and Store 4 to Store 6 migration guides are launch gates for 6.0.0.

Project

• Stability: API tiers, the deprecation cycle, release cadence, and verification.
• Roadmap: What remains before release and what follows.
• Community resources: Talks and interviews spanning both Store generations.