Repository navigation
Promote Weather and Pomodoro to built-in widgets #15
Description
Activity
Worth splitting this one — the two halves are not equally cheap.
Pomodoro is genuinely trivial. It is entirely local: a timestamp in storage, a countdown, an optional notification. Nothing about promoting it has consequences beyond moving code.
Weather has a consequence. README currently says:
Notchly does not collect analytics or make network requests of its own. Network access belongs to widgets and is disabled until you grant it.
That claim holds today precisely because weather is a custom widget behind the
networkpermission — the user grants it, and the request belongs to the widget. Making it built-in means Notchly itself calls Open-Meteo, and the sentence stops being true as written.Three ways out, in order of how much I would want them:
- Ship it built-in but off until the user sets a location, and reword the README to say Notchly makes no network requests until you ask it to. Honest, and keeps the feature.
- Leave weather custom and only promote pomodoro. Costs the comparison row.
- Ship it built-in and quietly drop the claim. Not worth it — the privacy line is a real reason people pick this over the alternatives.
Option 1 is probably right, but it is a product call rather than a refactor, which is why this is a comment and not a commit.
Both already exist and work — but they ship as examples, in a folder, found only by people who go looking.
Every competitor ships weather and a pomodoro as first-class features. Moving these into the built-in list changes nothing technically and closes two rows of the comparison against NotchNook, Boring Notch and Rainmeter.
Cheapest win on the widget roadmap.
The rule worth applying generally: a widget earns built-in status when it works for everyone the moment the app opens. It stays custom when it needs credentials, an account, or an administrator.