Skip to content

Protect KeyClash visitors: safe alternatives when Play availability is unverified - #130

Merged
appdevelopsk merged 8 commits into
mainfrom
growth/keyclash-quick-games-reentry-20261114
Nov 14, 2026
Merged

appdevelopsk merged 8 commits into
mainfrom
growth/keyclash-quick-games-reentry-20261114

Conversation

@appdevelopsk

@appdevelopsk appdevelopsk commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Issue found during release review

KeyClash was linked from its existing support page on Google Play, but its exact Play ID (com.keyclash.key_clash) could not be opened or found by public search. A third-party listing (AppBrain) says it was removed from Google Play June 17, 2026; official Play Console status is not available here, so that must be independently confirmed. Do not promote the application as available without a listing check.

Revised safe scope

  • Previous proposed additions of KeyClash cards to EN/JA Quick Games guides were fully reverted to their original main blobs; no new unverifiable Play CTA or structured data remains.
  • In /support/key-clash/ only, add visible user-help links to the existing EN and JA Quick Games guides and conditional wording for visitors whose Play Store does not list KeyClash in their region.
  • Preserve original support Play anchor for existing install-related help, but classify its existing single download_click event with app_slug=key-clash and placement=details for clean GA4 attribution; no duplicate new event.
  • Add four Node regression cases verifying original 5/4 Quick Games cards and JSON-LD remain unchanged, no KeyClash store promo added, EN/JA alternative links, existing canonical and single click event.

Verified

Exact GitHub branch readback of four files; twelve source invariants passed. Full browser test, Play Console publication/availability verification, production publish and active-user measurement are not possible with this tool connection and are not claimed.

Release guidance

Run node --test tests/keyclash-quick-games-journey.test.mjs in full checkout, verify mobile layout and help-site content, and manually deploy after approval. Separately use Play Console to confirm KeyClash availability; if delisted, change the existing support page's primary download CTA into an explicit unavailable status and offer alternatives. Do not add it to public acquisition guides until live Store availability is established.

Third-party report: https://www.appbrain.com/appstore/keyclash-typing-battle/ios-6759966415 .

@appdevelopsk appdevelopsk changed the title Grow app discovery: add KeyClash to English/Japanese Quick Games journeys Protect KeyClash visitors: safe alternatives when Play availability is unverified Nov 14, 2026
@appdevelopsk
appdevelopsk merged commit 0f65580 into main Nov 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant