Offline-first architecture
The customer app front end is a plan
simca-app holds only a plan: a Flutter interface over the Rust libraries through a generated bridge, with no business rules in the interface and screens in this order: cash sale, products and prices, tickets, end of day, elements, updates, settings. Nothing was scaffolded because Flutter could not be installed on the build machine. Old Windows 7 and 8.1 shops cannot run current Flutter, so the toolkit decision is tied to the hardware survey.
Designed in a document, no code yet
What to plan for
- Windows 7 and 8.1 support open
- Two toolchains per build
- Receipt printing not designed
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Low-literacy mode (icon-first UI) L10N-0028
- Narrow versioned contract between core and Logistics ARCH-0016
- Contract spec documents (both sides) ARCH-0017
- Contract: identity and keys ARCH-0018
- Contract: inventory (INV) ARCH-0019
- Contract: pricing (PRC) ARCH-0020
- Contract: delivery (DLV) ARCH-0021
- Contract: waybill and handshake (CONN) ARCH-0022
- Contract: bookkeeping (BK) ARCH-0023
- Contract: licensing flags (LIC) ARCH-0024
- Contract: backup and export (DATA) ARCH-0025
- Contract: notifications and tasks (TASK) ARCH-0026
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.