{
  "id": 16452658,
  "title": "Ask Your Closed Testers Twice: Day 1 and Halfway",
  "url": "https://urgent.news/2026/10/25/ask-your-closed-testers-twice-day-1-and-halfway",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-25T09:04:46.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/vmzavas/ask-your-closed-testers-twice-day-1-and-halfway-1pkg"
  },
  "original_language": "en",
  "account": "The author advises testing teams to ask closed testers two questions at different times during a 14-day test. The first question asks what testers expected to happen after the first tap, ideally on day 1. This is crucial to identify onboarding issues as the app still feels new. The second question asks what would bring testers back, due on day 7. Closed testers return because they promised to, not out of curiosity, so this question reveals repeat-use friction like expired logins or slow screens. The author stresses tagging feedback with device, Android version, and build context for clarity. After the test, the two sets of answers help identify onboarding fixes and factors influencing continued use. This two-question approach, applied to PeerPlay's 12 testers, directly informs Google's production application review process.",
  "summary": "In a recent post about getting more out of a tester swap, I gave developers a piece of advice that was half right. I suggested sending every tester the same short question, \"What did you expect to happen after the first tap?\", and asking it once, around the middle of the 14-day test. On Indie Hackers, a reader pointed out the flaw. By the middle of the test, the first tap is a week old. And the…",
  "key_points": [
    "Ask closed testers two questions at Day 1 and halfway (Day 7)",
    "First question reveals onboarding issues, second uncovers repeat-use friction",
    "Applied to PeerPlay's 12 testers, informs Google's production review process"
  ],
  "editors_take": "Splitting feedback collection into distinct onboarding and retention phases allows developers to isolate initial usability friction from the technical hurdles that prevent long-term user engagement during closed testing.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}