everkit-state
v0.6.0
Published
Reusable client-state + persistence primitives for React Native / Expo apps: a SecureStore-to-Zustand StateStorage adapter and a composable preferences (theme + onboarding) slice. The storage backend is injected by the consumer, so the core stays pure and
Maintainers
Readme
everkit-state
everkit-state helps our apps remember a few small choices a person makes, so the app looks and behaves the same way the next time they open it
The problem it solves
Every app needs to save choices like light or dark mode and load them again on the next launch. Without a shared piece, each app would solve this on its own, slightly differently, and a mistake fixed in one app would stay broken in the others
What an app gets
- A saved theme choice - light, dark, or follow the phone's own setting
- A saved welcome-tour flag - someone who already finished the introduction screens does not see them again
- Safe storage - choices are kept in the phone's secure storage area, the same place that holds passwords
- Only the right things saved - short-lived details, such as whether the app is still loading, are left out so every launch starts clean
- One shared, tested approach - Tea Companion, Dial It In and Matcha Companion use the same code, so one fix reaches all of them
An everyday analogy
Think of a filing folder with labelled sections. everkit-state decides what goes into the folder and how each section is labelled. Each app brings its own locked drawer to keep the folder in. Because the folder works in any drawer, it can be checked on an ordinary desk with no drawer at all, which is how it is tested
For developers: see ARCHITECTURE.md
