Hardware, platform and safety / Offline-first architecture
Where does “Launcher” fit in Simca, thinking about windows first?
Designed in a document, no code yet C0236
The one download. It is a regular program with no account of its own (ADR-0003). It installs, starts and updates Simca, shows a plain-sight Offline/Online toggle for the app's login mode and is the only place to pick, add or remove elements. When opened and connected it makes one disclosed update-manifest request and offers any update, even if the app is set to Offline. Groundwork exists as a tested library (spec writer, settings, signed update check, staging, rollback, offline install, removal choices) with a mock fetcher; there is no screen, no HTTP fetcher and no installer. Plan for: windows first; ios must match other platforms with apple limits checked later; shell technology not decided. 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
- How does Simca approach “Local logs and diagnostics”, considering support without telemetry?
- Which edge cases come up around “Offline mode”, in particular regarding clock skew?
- How does Simca approach “User-initiated signed updates”, considering power loss mid-update?
- See it in context with the whole topic
- Search all answers