Documentation Docs version: dev (Pre-release: Gitoodo has not been released yet)

For developers · Privacy and data

Voluntary support

On this page
  1. Where
  2. When the card shows
  3. Weekly review
  4. Channels (fail-closed)
  5. Addresses
  6. Storage

Gitoodo asks, rarely and quietly, whether someone wants to support its development. Supporting unlocks nothing; every feature works the same without it. The wording is "Unterstützen" / "support", never "Spende" / "donation" (the publisher is not a charity and issues no receipts).

Where#

  • Settings: the row "Entwicklung unterstützen" with a pink heart (settings-support) opens the support page. It is always there, also after "Nicht mehr fragen".
  • Footer heart (footer-support): a small pink heart at the trailing end of the status footer, in every view, opens the same page; label and tooltip "Entwicklung unterstützen". It is permanent and quiet (no badge, no counter, no animation) and does not count as an ask: the rules below stay unchanged.
  • Inline ask (support-ask): a card above the tab list after an answer was sent from the detail view, i.e. at the place of the success. No dialog, no focus move, nothing blocked. Its three actions: open the page (support-ask-open), "Später" (support-ask-later), "Nicht mehr fragen" (support-ask-never).
  • Weekly review (weekly-review-ask, #707): when the ask is due, the weekly review card (see below) may carry it instead, with the same three actions and the same wording; without payment links (Mac App Store or unknown channel) the text names only a star or a recommendation.

When the card shows#

Rules live in src/views/support/logic.ts (pure functions, tested with simulated time).

RuleValue
Earliest asknext success after 3 successes
Successes spread over at least2 different local days
Asks per installation, at most3
Pause after showing or "Später"90 days
Pause after opening a payment link270 days
"Nicht mehr fragen"final, no further asks

A success is an answer sent successfully from the detail view. Showing the card already counts as an ask and starts the 90-day pause, so a card closed by navigating away is not shown again on the next answer. Pauses only ever grow, never shorten. A payment click is never treated as a payment; the app does not know and does not track whether anyone paid.

One prompt per session, shared cap (#707, #712). The inline ask, the weekly review and the store rating request share one cap, kept by the Rust core (crates/core/src/asks.rs, ledger in asks.json): at most one prompt per app session, and at least 14 days between two asks in both directions. Whichever claims it first is the only prompt until the next start.

  • The inline card claims the cap through claim_support_ask, and only when its own rules (askAllowed) already allow an ask; with a closed cap the success still counts but no card shows.
  • The weekly review claims it through claim_review (offerReview in src/views/support/logic.ts). It always takes the session's one prompt. It carries the ask only when reviewAsk allows it (the same askAllowed limits) and 14 days have passed since the last ask; then it counts as a support ask in the shared cap and is recorded with recordAsk (one ask, 90-day pause), exactly like the inline card. A review without the ask does not start the 14-day spacing, otherwise the weekly card would hold every other ask.
  • Answers to the card ("Später", "Nicht mehr fragen", a payment link) only change support.json; they never reach the cap or the rating state (no review gating).

The thresholds are a hypothesis for this app: answering questions is rarer than the operations other apps count, so "3 answers over 2 days" stands for experienced use. Revisit them if the card turns out to come too early or never.

Weekly review#

Once a week a calm card (weekly-review) appears above the list: answered questions, median answer time, merged pull requests and closed issues of the last 7 days, computed on the device from the user's own forge data (loop_metrics, see docs/metrics.md). Rules live in src/views/review/model.ts (pure, tested):

  • On by default; "Wochenrückblick" in Settings → Notifications (settings-weekly-review) or "Wochenrückblick ausschalten" on the card switches it off (weekly_review in settings.json).
  • The first start only remembers the current week; the first review comes the week after.
  • The week starts on the region's first weekday. The week it was offered in is kept in localStorage (gitoodo.weeklyReview.week); "Schließen" ends it for that week.
  • A week without answers, merges or closed issues shows nothing and counts as done.
  • When another prompt already showed in this session, the review waits for a later session of the same week.

Channels (fail-closed)#

supportChannel() maps the build variant (build_variant command) to a channel; supportWays() decides what the page shows.

ChannelPayment linksStar and share
Direct download (macOS outside the App Store)PayPal, Ko-fi, GitHub Sponsors; Buy Me a Coffee behind "Weitere Wege"yes
Windows installer and Microsoft Store (MSIX)same as direct (Microsoft Store Policy 10.8.2 allows third-party payments)yes
Mac App Storenone, and no mention of them in any text (Guideline 3.1.1)yes
Any other OS, unknown build, or still loadingnoneyes

Addresses#

The default payment addresses live in one file, src/views/support/destinations.ts; the app reads them through src/views/support/links.ts, and the project URL is shared with the About section. The landing page imports the same file and the app's support texts (src/i18n/support.ts and its locales) in every site language. GitHub's "Sponsor" button (.github/FUNDING.yml) and the README's "Support" section cannot import it; tests/support-links.test.ts fails when either drifts from it. A distributor can replace or clear each payment address at build time: VITE_SUPPORT_PAYPAL_URL, VITE_SUPPORT_KOFI_URL, VITE_SUPPORT_GITHUB_URL, VITE_SUPPORT_BMAC_URL. An empty value or anything that is not https:// counts as missing: the way is hidden and the page names what is missing (support-missing).

The project has no NETWORK.md. The support feature adds these external addresses; they are only opened in the external browser on a click, never fetched by the app:

  • https://www.paypal.com/donate/…
  • https://ko-fi.com/silviol
  • https://github.com/sponsors/silvio-l
  • https://buymeacoffee.com/silvio.lindstedt
  • the project URL (star)

Provider logos are local SVGs in src/assets/support/ (origin and licence in its README); no hotlinking, no third-party scripts or widgets.

Storage#

The ask state (successes, days, asks, pause, declined) is stored by the Rust core in support.json in the app data directory (crates/core/src/store/support.rs), read leniently and written atomically. The shared ask cap lives in asks.json (crates/core/src/store/asks.rs). Neither file is part of the settings export, and neither is part of the usage statistics (docs/privacy.md). There is no payment code.

Docs version: dev