Hardware, platform and safety / Offline-first architecture
How does Simca approach “iOS launcher parity”, considering replacing app files?
Designed in a document, no code yet C0247
ADR-0002: the iOS launcher must look and work like the other platforms; Apple rule limits are checked later and recorded as per-feature exceptions instead of being designed around now. Plan for: replacing app files; loading code; per-feature exceptions. 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 goes wrong with “Free start and the profit threshold” in a shop, with a focus on selling never stops because of the fee?
- What goes wrong with “Offline guard tests” in a shop, thinking about new dependencies need an allowlist entry?
- Where does “The launcher's one opening request” fit in Simca, in particular regarding network address visible to the host?
- See it in context with the whole topic
- Search all answers