Hardware, platform and safety / Offline-first architecture
How does Simca approach “Data model”, especially around schema changes?
Built in the repository (checked files or tested library code; not a product you can run yet) C0232
The app core stores data in SQLite (write-ahead logging, full sync, integrity check at open, verified backups) with forward-only migrations that come from each element's pack; Logistics has its own database file. This exists as tested library code, with no screen. A changed shipped migration is refused, and no encryption at rest exists yet (an open decision). Plan for: schema changes; encryption at rest is open; kept data after removal. It exists only as a file in the repository, not as a product feature.
How to read this
The tag above says how real the answer is. Answers describe the plan in the repository and design documents. No app is released. Where an answer touches tax or law, treat it as a theme to verify with a qualified local adviser.
More in Offline-first architecture
- Why does “Performance goals” matter for a small business, in particular regarding old hardware?
- Is “Update model” supported today, especially around updating offline?
- Why does “Localization” matter for a small business, thinking about translation quality?
- See it in context with the whole topic
- Search all answers