Native reviews and optional feedback

Choose a calm moment after the user has experienced enough of the product to give useful feedback. Make review eligibility independent of satisfaction, predicted rating, purchase status, support history, or survey answers. The existing skill name is retained for compatibility; it does not authorize sentiment routing.

Product contract

A documented usage milestone + a shared cooldown
  → request the platform's native review flow
  → resume the normal app experience

Settings → Review this app → user-initiated store link
Settings → Send feedback → optional feedback/support for everyone

A completed task or level can be a usage milestone. Do not infer approval from task completion. Apply the same eligibility and cooldown rules to everyone; do not use earlier sentiment answers to filter users or delay their access to reviews. Keep feedback independent of the review journey and available regardless of rating, sentiment, or whether a review request was attempted.

Platform rules and references