[appdevelopsk]

Acquisition hypothesis

Our official /apps page has 92 Play-published titles in a single long alphabet/installation list, but no search, goal categories, or conversion measurement. It is discoverable in web search, so this is a deployable acquisition improvement instead of adding another in-app feature without retention evidence.

Shipped source changes

• Add accessible instant text search and curated goal filters to the server-rendered catalog; the existing 92 organic-search-readable cards and Play Install Referrer URLs remain unchanged.
• Add two detailed content guides (/guides/quick-games/, /guides/daily-habits/) with unique choice advice, four existing verified-visible Play apps each, canonical and OG tags, truthful structured ItemList, tracked store links, accessible responsive design, sitemap registration, and internal links from the catalog. No fabricated reviews, prices, features or unpublished apps.
• GA4 first-party catalog_search_used, catalog_filter_used, catalog_store_click, guide_store_click; never send raw user search terms. Existing GA4 property reused. Site is the acquisition source; store acquisition and app first-value remain downstream.
• Add Node behavior/contract tests, CI workflow and build_catalog.py --check to ensure generator idempotence on all future changes.

Release and evaluation

PR merge updates source; verify Pages publication separately. After rollout: measure organic landing views -> filter/search engagement -> store-click per app/guide -> Google Play listing visitors/acquisitions -> GA4 first value/D1. Compare 28-day windows and use mature cohorts; do not claim increased user count before data. Avoid distributing hidden/unpublished apps.