Architecture first
A clean, modular core with deliberate boundaries—designed to stay understandable as products and teams grow.
Use simple flat keys for app state, isolated typed collections for offline entities, and one durable pure-Dart engine underneath both workflows.
Preference exists because durable local state should not force teams to choose between a tiny key-value utility and a heavy database stack.
A clean, modular core with deliberate boundaries—designed to stay understandable as products and teams grow.
Fast paths, minimal overhead and purposeful APIs keep local data work responsive without turning your app into infrastructure.
Durable app state and typed offline entities live close to the user, with a foundation built for the sync era ahead.
Thoughtful failure modes, predictable behavior and strong validation aim for the reliability real applications demand.
Small APIs, useful defaults and readable code let teams focus on the application instead of storage ceremony.
Preference is being built as a cohesive ecosystem—not a collection of utilities that drift apart over time.
Use direct get/set APIs for settings, flags and lightweight values. Use named collections and serializers for work orders, assets, notes or any domain model that needs structure and scale.
Durable local-first storage for app state and typed offline entities.
Inspect Preference databases through a focused desktop workspace built for debugging, validation and the Flutter VM Service.
Scroll to assemble the Studio
Download Preference Studio 0.1.0 for read-only inspection of `.pref` files and live Flutter VM Service connections.
Preview installers are unsigned. Verify the published SHA-256 checksums before installation.