docs: capture agent field notes; drop RuStore-steering for the GP variant
CI / changes (pull_request) Successful in 3s
CI / unit (pull_request) Has been skipped
CI / integration (pull_request) Has been skipped
CI / ui (pull_request) Has been skipped
CI / conformance (pull_request) Has been skipped
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Has been skipped

This commit is contained in:
Ilia Denisov
2026-07-11 22:53:26 +02:00
parent edaf2dfd9e
commit 0c5e40c509
3 changed files with 192 additions and 6 deletions
+7 -6
View File
@@ -459,12 +459,13 @@ One codebase, two build variants selected by flags:
difference is that purchases are hidden — the flag structure (`purchasesHidden()`) already carries
both cases, so no repaint is needed.
**Open compliance item to settle when the GP build is actually built (deferred, not now):** Google
forbids not just external billing but *steering* users to other payment methods or app stores. The
existing `isGooglePlayBuild()` stub "points the user to the RuStore build" — that steering likely
violates Google policy. When building for GP, change the stub to a neutral "not available here" with
no pointer to RuStore. Tracked here so it is not forgotten; it does not affect the RuStore MVP. Google
Play also requires an **AAB** (not APK) and its own signing/Play App Signing — a separate CI target.
**Google Play compliance — decided: no RuStore steering.** Google forbids not just external billing
but *steering* users to other payment methods or app stores. So the Google Play build hides purchases
with **no** pointer to RuStore: the existing `isGooglePlayBuild()` RuStore-pointer stub is **dropped**
in the GP variant (show nothing, or a neutral pointer-free message — never name or link RuStore or any
other store). This does not affect the RuStore MVP (there `isGooglePlayBuild()` is false, so the stub
never shows). Google Play also requires an **AAB** (not APK) and Play App Signing — a separate CI
target, built later.
---