# MobileNativeFoundation/Store

A library for reading and writing data that lives in network, disk, and memory.

Repository: https://github.com/MobileNativeFoundation/Store
Canonical: https://ross.abutalabs.com/products/mobilenativefoundation-store
Homepage: https://store.mobilenativefoundation.org
Language: Kotlin
License: Apache-2.0
License Family: permissive
Topics: offline-first, cache, kotlin-multiplatform, kmp, kotlin-flow, kotlin-multiplatform-mobile, kotlin-native, repository-pattern, fetch, update
Last push: 2026-08-24T08:48:43+00:00

## Health v2 (maintenance only)
Score: 89/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 69, longevity 100
- inputs: {"age_days": 2463, "days_push": 9, "days_rel": 51, "gap_med": 156.0, "n_releases_24m": 5}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 3416, forks 215 (observed 2026-08-28T04:08:03.723501+00:00)

## What it is
Store5 is a Kotlin Multiplatform library that provides a unified architecture for fetching, caching, and updating data across network, memory, and disk layers. It acts as a single source of truth with smart caching, full CRUD support via MutableStore, and offline-first synchronization.

## Use cases
- build an offline-first mobile app with local caching
- cache API responses in memory and on disk in Kotlin
- implement a repository pattern with a single source of truth
- sync local database with remote API data
- fetch data only when memory and disk caches miss
- handle CRUD operations with automatic local-remote synchronization
- share data-layer logic between Android and iOS with Kotlin Multiplatform

## When to choose
- you're building a Kotlin Multiplatform or Android app needing layered caching
- you want offline-first behavior with automatic network/disk/memory fallback
- you need consistent data flow and reduced boilerplate around fetching and caching

## When to avoid
- your project isn't Kotlin-based
- you need a full database rather than a caching/data-flow layer
- you want a turnkey sync solution without writing fetcher/source logic

## Facets
- artifact type: library
- maturity: active
- function: caching, database, http-client, state-management
- domain: mobile-development, cross-platform
- platform: jvm
- tags: kotlin-multiplatform, offline-first, repository-pattern, kotlin-flow, single-source-of-truth, data-synchronization, data-engineering, android, ios, mobile

## Member repositories
- MobileNativeFoundation/Store (main) score 89

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:03.723501+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:38:14.941751+00:00, confidence not recorded.
  - readme: https://github.com/MobileNativeFoundation/Store (fetched 2026-08-28T04:08:03.723501+00:00, sha 7c4a38b9b00e)
  - homepage: https://store.mobilenativefoundation.org (fetched 2026-08-29T09:32:17.264202+00:00, sha 92c30870cc76)
  - site_page: https://store.mobilenativefoundation.org/docs/intro (fetched 2026-08-29T09:32:17.274220+00:00, sha fa9ae243b82a)
  - site_page: https://store.mobilenativefoundation.org/docs/quickstart (fetched 2026-08-29T09:32:17.277099+00:00, sha 91b13ab02742)
- Data as of 2026-08-30T08:39:29.467469+00:00.