Hardware, platform and safety / Offline-first architecture
What should I plan for with “Update notice”, with a focus on the request reveals the network address to whoever serves?
Designed in a document, no code yet C0245
ADR-0003 replaced the earlier rule that nothing is contacted until the user presses Check. Whenever the launcher is opened and connected it makes one disclosed update-manifest request (a plain GET of a signed static file, no account data) and shows any update in a visible, dismissible notice. There is no polling afterwards. A manual Check repeats the request. A setting to turn off even the opening request is implemented in the library as recommended and its default is for the owner to confirm. Plan for: the request reveals the network address to whoever serves the file; dismissed until a newer version is known; setting to disable the request. 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
- Which edge cases come up around “Offline/Online toggle”, in particular regarding lost device key?
- What goes wrong with “Free start and the profit threshold” in a shop, with a focus on selling never stops because of the fee?
- How does Simca approach “iOS launcher parity”, considering replacing app files?
- See it in context with the whole topic
- Search all answers