[EPIC - ANDROID] In-App Rating & Feedback Loop

[JorenC]

Feature Specification: In-App Rating & Feedback Loop

1. Objective

To improve app visibility and store ranking by encouraging active players to provide ratings, while simultaneously creating a high-signal channel for product improvements.

2. Logic & Triggering

To ensure feedback comes from engaged users and to avoid "churn-based" low ratings, the prompt will only trigger after a specific user milestone.

• Trigger: The rating flow will be gated by a device-specific flag. The request will trigger only after the user has completed their first full game session.
• Purpose: This ensures the user has experienced the core mechanics of the game before being asked for an evaluation.

3. Feedback Workflow

We will implement an in-app evaluation flow to distinguish between constructive criticism and public store reviews:

Step 1: The Initial Prompt

The user is presented with a rating request. The messaging will transparently frame the game as a passion project developed by a small two-person team, emphasizing that honest feedback is crucial for our continued development.

Step 2: Conditional Routing

• 1–3 Stars: The user is directed to an internal feedback form ("How can we make this better?"). Responses are routed to an independent log for analysis. This provides us with actionable data to prioritize development tasks.
• 4–5 Stars: The user is thanked for their support and presented with a direct link to the Google Play Store (and Apple App Store) to finalize their review.

4. Implementation Notes

• Data Utilization: We will monitor the internal feedback logs to identify recurring pain points. We plan to use automated analysis to summarize top-requested improvements on a weekly basis.
• Ethical Consideration: While this multi-step flow is a common industry practice, we will ensure that the internal feedback form is genuine and that the data collected is actively used to inform our product roadmap, turning the potential "dark pattern" into a genuine tool for user-centric development.

[johnpooch]

Should we simultaneously add this for iOS as well? We can even add it for the web as well. Obviously, for the web, we wouldn't link them to the Play Store or the App Store, but we could still record the rating.

I think we should take a quick look at the number of users that have used the app and how many would meet the criteria for the feedback form to appear. When we look at the numbers, we should ask ourselves how many responses we think we will realistically get, and then consider whether this is worth adding at this time.

[JorenC]

I think the reason for Android/iOS is virality - if we get consistent reviews (and if those reviews are positive), I believe the Store will start recommending this game. So - even with a smaller number of players (which would grow as our player base grows) I think it's worth it. For web, I'm not so sure. It's nice as a feedback loop - but maybe a bit further down the line - with reddit/discord we do have a lifeline in the community, and it might be a bit overkill. And - if there is no specific bias for mobile, we'd get bugs/errors/issues through the other channels anyway. - IF we implement, I think it's then good to see how many players would be eligible - but even a small number would be worth it, IMO.

…

On Mon, Jun 22, 2026 at 3:22 AM John McDowell ***@***.***> wrote: Should we simultaneously add this for iOS as well? We can even add it for the web as well. Obviously, for the web, we wouldn't link them to the Play Store or the App Store, but we could still record the rating. I think we should take a quick look at the number of users that have used the app and how many would meet the criteria for the feedback form to appear. When we look at the numbers, we should ask ourselves how many responses we think we will realistically get, and then consider whether this is worth adding at this time. — Reply to this email directly, view it on GitHub <#786?email_source=notifications&email_token=ABXURGK3CKCOTXWR5F3KGID5BCC5LA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTHA3DCNJSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17386152>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXURGN5YFTBSR5UMYI6I4L5BCC5LAVCNFSNUABIKJSXA33TNF2G64TZHM4TAMRZGA4DMMRQHNCGS43DOVZXG2LPNY5TCMBSG44TMMBTUF3AE> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>