Hardware, platform and safety / Offline-first architecture
How does Simca approach “Elements, not roles”, with a focus on menu entries only from included elements?
Designed in a document, no code yet C0224
ADR-0001 removed separate role builds. One product, many elements; unselected elements are not compiled in. Presets such as store, bodega or driver are only pre-ticked selections. Plan for: menu entries only from included elements; free pricing class; permissions inside the app are ordinary permission sets. It is designed in a document and no code exists.
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
- What should I plan for with “Online sign-in”, with a focus on sign-in method not decided?
- Why does “Paired development” matter for a small business, thinking about thin manifests with no business logic?
- Where does “Build delivery” fit in Simca, with a focus on cache integrity on every read?
- See it in context with the whole topic
- Search all answers