Hardware, platform and safety / Offline-first architecture
Why does “What the app core can do today” matter for a small business, considering no user interface?
Built in the repository (checked files or tested library code; not a product you can run yet) C0252
The Simca core is Rust library code, tested, with no screen: money in integer minor units with cash rounding, a SQLite store, and seven elements (products and stock ledger, price lists, sale with cash settlement and void, open tickets, takeout orders, double-entry books, waybills with receiving into stock). Only cash payment exists, quantities are whole units, and there is no printing, hardware, card payment, fiscal document, encryption at rest or permission logic yet. Plan for: no user interface; cash only; whole-unit quantities. 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
- Where does “Simca's own launcher, forked from an earlier private one” fit in Simca, especially around reuse terms of the source not confirmed?
- Which edge cases come up around “What the Logistics core can do today”, considering reputation math is a draft?
- What should I plan for with “The quarterly cost model”, with a focus on no margin means no cushion for higher costs?
- See it in context with the whole topic
- Search all answers