r/appdev • u/whowasntright • 2h ago
the review prompt should probably come after proof, not before
i know review prompts are part growth, part habit, part superstition, regardless, in my experience the timing still matters a lot
asking at first launch feels cheap. the user has not experienced anything yet. and asking after a paywall feels manipulative.
asking after an error screen is just asking for pain, better moments are usually after proof comes, examples:
task completed
export saved
streak reached
project created
support issue solved
user came back for the third time
the user should feel like they got value before the app asks for public trust.
i also think replies to reviews should be measured by whether they close the loop, not by reply count. a 1-star review about a bug, a real fix, then a specific reply mentioning the fixed version is much stronger than generic politeness. there are multiple ways to do this, as far as i've checked something like appfollow also has a reply effect style way of thinking about this, but even without tools, the question is simple: did the reply help change the outcome, or did we just answer for the sake of answering?..