You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: _posts/2024-12-26-play-store-rating-prompt.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ So, why add complexity to a fairly simple to use library? Well, there are a few
69
69
### Requirements
70
70
71
71
1.**Simple to use**: Any ViewModel that wants to display a review prompt shouldn't need to keep track of the request status, handle errors etc. It should just be able to request the prompt's appearance, and optionally pre-load.
72
-
2.**Remotely configurable triggers**: I want to be able to remotely control where this prompt appears. For example, I may want to disable it appearing after a successful bud due to some unrelated technical issue.
72
+
2.**Remotely configurable triggers**: I want to be able to remotely control where this prompt appears. For example, I may want to disable it appearing after a successful bid due to some unrelated technical issue.
73
73
3.**Triggered on button click or without specific interaction**: The review prompt should be triggerable by a variety of trigger types`^`.
74
74
4.**Able to remotely disable**: In case there's some catastrophic issue in Google's library, I want the ability to ensure it isn't relied upon at all if there's no enabled triggers.
75
75
5.**Requests aren't spammed**: Whilst Google [doesn't explicitly state quotas](https://developer.android.com/guide/playcore/in-app-review#quotas), they do say:
0 commit comments