From b8968f5e19e13632a49793f8630865ba24fcd4b3 Mon Sep 17 00:00:00 2001 From: Jean-Luc Makiola Date: Thu, 22 Oct 2026 11:12:18 +0200 Subject: [PATCH] docs(roadmap): settle the Wear OS note on what the docs say MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Keep §5's own claim that only crash reports leave the phone, say the dependency would ship in every channel, and keep the standalone app's distribution caveat. Refs #27 --- docs/ROADMAP.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md index 51b0f26..865acbc 100644 --- a/docs/ROADMAP.md +++ b/docs/ROADMAP.md @@ -621,10 +621,9 @@ Deferred deliberately, in rough priority order: blocked on a privacy and distribution decision. A watch that shows and controls the phone's timers and next alarm needs a phone-to-watch channel. The usual one, Google Play Services' Wearable Data Layer, is a "third-party - service" that `docs/PRIVACY.md` §2 rules out, and with no product flavours it - would also be a non-free dependency in the build F-Droid makes. A channel of - our own (Bluetooth, since there is no INTERNET permission) avoids the - dependency but needs Bluetooth permissions and is a new way for data to leave - the phone, beside Auto Backup and crash reports (`PRIVACY.md` §4 and §5). A - standalone watch app with its own timers and alarms avoids all of this but - doesn't control the phone. + service" that `PRIVACY.md` §2 rules out, and with no product flavours it + would ship in every channel, F-Droid included. Any channel of our own would + need new permissions (`PRIVACY.md` §7) and would be a way for data to leave + the phone, which §5 says only crash reports are today. A standalone watch app + with its own timers and alarms needs neither, but doesn't control the phone + and has no F-Droid route onto a watch.