Friend install and update docs #56

Closed
opened 2026-08-03 22:43:05 +00:00 by TheAnachronism · 1 comment

Part of #41
Blocked by: #52, #54, #55

Question

What is the minimum install/update documentation a friend needs to sideload and stay current on 1.0 beta?

Part of #41 Blocked by: #52, #54, #55 ## Question What is the minimum install/update documentation a friend needs to sideload and stay current on 1.0 beta?
Author
Owner

Resolution

Install / update docs bar for sideload 1.0 beta (criteria only — write later):

Must — docs/install.md

Short how-to for installers / users / sideload testers. Do not use the word “friend” in this prose.

  1. Get the APK — download from this repo’s Forgejo Releases; expect asset stem tt-rss-viewer-…. Stay channel-agnostic in the criteria (exact tag prefix filled after Release channel for beta, or say “the 1.0 beta release”).
  2. Install on Android — allow installs from this source / unknown apps; install the APK; open tt-rss Viewer.
  3. Sign-in / API prerequisite — need a self-hosted tt-rss with API enabled (ENABLE_API_ACCESS), plus base URL, username, and password.
  4. How to update — later APKs from Releases install over the current one when offered; check Releases for updates. No in-app updater (Signing and update trust).
  5. Privacy must-disclose — password + sid stored on-device for silent re-login; network only to the user’s own tt-rss (Privacy surface for friends).
  6. Alpha → beta reinstall note — plain language: if an older alpha build was installed, uninstall may be required before installing beta (different app identity). No certificate/signing jargon (App identity and versioning, Signing and update trust).

README points here per Contributor and user docs bar; do not duplicate the full how-to in README.

Not must for beta

  • Screenshots / per-OEM unknown-apps walkthroughs
  • Troubleshooting encyclopedia
  • Document-band known-issues section (that inventory stays in the polish/readiness bar)
  • Operator keystore / signing-cert prose

Why

Sideload testers need a single short page that gets them from Releases → installed → signed in → updated, with the privacy and one-time reinstall facts already locked — not a full support manual.

## Resolution **Install / update docs bar** for sideload **1.0 beta** (criteria only — write later): ### Must — `docs/install.md` Short how-to for installers / users / sideload testers. **Do not** use the word “friend” in this prose. 1. **Get the APK** — download from this repo’s Forgejo Releases; expect asset stem `tt-rss-viewer-…`. Stay **channel-agnostic** in the criteria (exact tag prefix filled after [Release channel for beta](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/57), or say “the 1.0 beta release”). 2. **Install on Android** — allow installs from this source / unknown apps; install the APK; open **tt-rss Viewer**. 3. **Sign-in / API prerequisite** — need a self-hosted tt-rss with API enabled (`ENABLE_API_ACCESS`), plus base URL, username, and password. 4. **How to update** — later APKs from Releases install over the current one when offered; check Releases for updates. No in-app updater ([Signing and update trust](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/54)). 5. **Privacy must-disclose** — password + `sid` stored on-device for silent re-login; network only to the user’s own tt-rss ([Privacy surface for friends](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/55)). 6. **Alpha → beta reinstall note** — plain language: if an older alpha build was installed, uninstall may be required before installing beta (different app identity). No certificate/signing jargon ([App identity and versioning](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/52), [Signing and update trust](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/54)). README points here per [Contributor and user docs bar](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/issues/51); do not duplicate the full how-to in README. ### Not must for beta - Screenshots / per-OEM unknown-apps walkthroughs - Troubleshooting encyclopedia - Document-band known-issues section (that inventory stays in the polish/readiness bar) - Operator keystore / signing-cert prose ### Why Sideload testers need a single short page that gets them from Releases → installed → signed in → updated, with the privacy and one-time reinstall facts already locked — not a full support manual.
Sign in to join this conversation.
No description provided.