Closed reedes closed 1 year ago
Probably best done with a partitioned data store, where the Watch partition carries only the most recent historical data, and the universal app (iOS/iPadOS/macOS) partition contains the full record. This will limit storage needs on watch hardware.
The universal app could routinely purge the watch app's partition of historical data once synced, as a possible design.
Added archiveID (UUID) to the two entities in the data model, in preparation.
Initialization code also added.
Updating existing data also added.
Currently there is no history log.
It could be useful to maintain a history of routines, along with charting of progress.
However the tradeoff is a database that bloats over time.
Perhaps this is best done in an iOS app that can better tolerate a large database?