9 lines
734 B
Markdown
9 lines
734 B
Markdown
 
|
# Local-first storage in SQLite (drift), with UUIDs for later sync
|
||
|
|
|
||
|
|
CookIt keeps the whole Recipe collection on the device in a SQLite database accessed through drift, with no server. One cook on one Android phone doesn't need a backend, and the Recipe Bundle export is the backup. Every record gets a UUID rather than an auto-increment integer so a sync service can be added later without rewriting IDs or references.
|
||
|
|
|
||
|
|
## Considered Options
|
||
|
|
|
||
|
|
- **sqflite**: no code generation, but queries aren't checked at compile time and watch streams have to be wired by hand.
|
||
|
|
- **JSON files**: simplest, but weak once Meal Plans reference Recipes.
|
||
|
|
- **Cloud backend from day one** (Supabase/Firebase): not worth running for a single user in v1.
|