scan: remote config, feature flags and remote paywalls not told to review (App Review 2.3.1, Play Deceptive behavior): remote-features finding for both stores, medium, with deep links, unless the review notes mention them; check prints it as a warning, validate carries it; warn only, the templates get a commented example line; code obfuscators a low note, minify alone nothing; store-pitfalls 74
This commit is contained in:
parent
9ba97b7e29
commit
61cb3338e8
13 changed files with 258 additions and 6 deletions
|
|
@ -87,6 +87,9 @@ Plain, polite, specific; one guideline per paragraph; no blame, no threats, no "
|
|||
- **2.3 Accurate metadata**: screenshots must show the real app (for a game: real gameplay); no prices, no "free"
|
||||
claims for paid items, no other platforms' UI; keywords without competitor names; age rating answers that match
|
||||
the content.
|
||||
- **2.3.1 Hidden or undocumented features** (Play: Deceptive behavior): remote config, feature flags or a remote
|
||||
paywall the review notes did not mention (`storebound scan` rule `remote-features`, store-pitfalls 74). Fix: say in
|
||||
the notes which SDK changes what remotely; a business-model change needs a new review and a description update.
|
||||
- **3.1.1 In-app purchase**: digital goods only through IAP; a visible **Restore Purchases** for non-consumables;
|
||||
no links to outside payment; loot boxes must show odds.
|
||||
- **3.1.2 Subscriptions**: the purchase screen shows title, length, price per period and what the user gets; links to
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue