Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance in-app reviews logic #20820

Closed
irfano opened this issue May 15, 2024 · 1 comment · Fixed by #20891
Closed

Enhance in-app reviews logic #20820

irfano opened this issue May 15, 2024 · 1 comment · Fixed by #20891

Comments

@irfano
Copy link
Member

irfano commented May 15, 2024

Currently, we show an in-app review prompt after the second post has been published, and only once. However, we’re overlooking users who manage sites or only read without publishing.

Required changes

  • If “LATER” is tapped on the old dialog, do not show the new prompt for 7 days.
  • If “NO THANKS” is tapped on the old dialog, do not show the new prompt at all.
  • If “RATE NOW” is tapped on the old dialog, reset the counters of the new prompt.
  • When the old dialog is shown, reset the counters of the new prompt.
  • Keep the old method but focus only on the happiest moments for the new prompt, since we can’t ask “Enjoying the app?” with the new prompt. So, update the new prompt logic with:
    • (Already existing): The second post is published OR
    • “like”, “comment like” and “follow” notifications are tapped 10 times in total.
  • Reset the counters and wait for 7 days after the in-app review prompt is shown. (If the user has already rated, the prompt will not show up but only Google can control this behavior.)

Link for internal discussion: pc8eDl-1nq-p2#comment-1088

@dangermattic
Copy link
Collaborator

Thanks for reporting! 👍

@irfano irfano self-assigned this May 16, 2024
@irfano irfano mentioned this issue May 28, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants